Bootstrapped and tested on x86_64-unknown-linux-gnu, applied.
Richard.
2017-03-14 Richard Biener
PR tree-optimization/80030
* tree-vect-stmts.c (vectorizable_store): Plug memleak.
Index: gcc/tree-vect-stmts.c
==
On Tue, Mar 14, 2017 at 6:32 AM, NightStrike wrote:
> On Mon, Mar 13, 2017 at 5:01 AM, Janne Blomqvist
> wrote:
>> On Sun, Mar 12, 2017 at 10:46 PM, Janne Blomqvist
>> wrote:
>>> On Sun, Mar 12, 2017 at 7:26 PM, NightStrike wrote:
On Mon, Feb 27, 2017 at 6:15 AM, Janne Blomqvist
wrot
Ping.
On Tue, Mar 07, 2017 at 06:10:48PM +0100, Marek Polacek wrote:
> In this testcase we have
> C c = bar (X{1});
> which store_init_value sees as
> c = TARGET_EXPR .n=(&)->i}>)>
> i.e. we're initializing "c" with a TARGET_EXPR. We call replace_placeholders
> that walks the whole tree to subst
On 03/13/2017 04:16 PM, Richard Biener wrote:
> On Mon, 13 Mar 2017, Martin Liška wrote:
>
>> On 03/13/2017 02:53 PM, Richard Biener wrote:
>>> On Mon, 13 Mar 2017, Martin Liška wrote:
>>>
On 03/13/2017 02:01 PM, Richard Biener wrote:
> On Mon, 13 Mar 2017, Richard Biener wrote:
>
>>>
On Tue, 14 Mar 2017, Martin Liška wrote:
> On 03/13/2017 04:16 PM, Richard Biener wrote:
> > On Mon, 13 Mar 2017, Martin Liška wrote:
> >
> >> On 03/13/2017 02:53 PM, Richard Biener wrote:
> >>> On Mon, 13 Mar 2017, Martin Liška wrote:
> >>>
> On 03/13/2017 02:01 PM, Richard Biener wrote:
>
On Mon, Mar 13, 2017 at 6:16 PM, Denis Khalikov
wrote:
> Hello everyone, i have a patch for this issue.
Great!
> List of implemented functionality:
>
> 1.Reading .gnu_debuglink section from ELF file:
> a. Reading name of debug info file.
> b. Verifying crc32 sum.
>
> 2. Searching for separate
On 2017.03.13 at 23:24 +0100, Thomas Koenig wrote:
> Hello world,
>
> Following Richard's suggestion, I have implemented the GFC_ASSERT macro
> and used it to (hopefully) silence the ominous warning and allow
> further optimization.
Unfortunately the single GFC_ASSERT isn't enough:
libgfortran/i
On Tue, Mar 14, 2017 at 1:04 AM, Bill Schmidt
wrote:
> Hi,
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79908 shows a case where
> pass_stdarg ICEs attempting to gimplify a COMPLEX_EXPR with side
> effects as an lvalue. The expression is not addressable, so the
> gimplification fails. This p
On Tue, Mar 14, 2017 at 1:37 AM, Martin Sebor wrote:
> Ping: this a P3 regression targeted at 7.0.1. It was found
> on x86_64-apple-darwin10.8.0 but affects all targets (even
> if it doesn't happen to manifest on them):
>
> https://gcc.gnu.org/ml/gcc-patches/2017-03/msg00342.html
I think you n
On 03/14/2017 09:13 AM, Richard Biener wrote:
> On Tue, 14 Mar 2017, Martin Liška wrote:
>
>> On 03/13/2017 04:16 PM, Richard Biener wrote:
>>> On Mon, 13 Mar 2017, Martin Liška wrote:
>>>
On 03/13/2017 02:53 PM, Richard Biener wrote:
> On Mon, 13 Mar 2017, Martin Liška wrote:
>
>
On Tue, 14 Mar 2017, Martin Liška wrote:
> On 03/14/2017 09:13 AM, Richard Biener wrote:
> > On Tue, 14 Mar 2017, Martin Liška wrote:
> >
> >> On 03/13/2017 04:16 PM, Richard Biener wrote:
> >>> On Mon, 13 Mar 2017, Martin Liška wrote:
> >>>
> On 03/13/2017 02:53 PM, Richard Biener wrote:
>
On 14.03.2017 09:27, Richard Biener wrote:
> On Mon, Mar 13, 2017 at 6:16 PM, Denis Khalikov
> wrote:
>> Hello everyone, i have a patch for this issue.
>
> Great!
>
>> List of implemented functionality:
>>
>> 1.Reading .gnu_debuglink section from ELF file:
>> a. Reading name of debug info file.
On 13.03.2017 18:26, James Cowgill wrote:
> Hi,
>
> On 11/03/17 12:11, Arnaud Charlet wrote:
>>> This patch fixes an error caused by my changing of the signal constants
>>> on MIPS in r244026. While that patch worked on mipsel, ada fails to
>>> bootstrap with it on mips64el with the error:
>>>
>>>
On Thu, Mar 09, 2017 at 02:06:16PM -0800, Andrew Pinski wrote:
> On Thu, Mar 9, 2017 at 6:42 AM, Wilco Dijkstra wrote:
> > Hi,
> >
> > Recently we've put a lot of effort into improving ifcvt to use CSEL on
> > AArch64. In https://gcc.gnu.org/ml/gcc-patches/2015-11/msg01639.html
> > James determi
On Mon, Mar 13, 2017 at 4:19 PM, Martin Liška wrote:
> Hello.
>
> This is a small follow-up patch, where local.local flag should be also dropped
> for a default implementation.
>
> Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
>
> Ready to be installed?
I see we have cler
On 03/14/2017 10:12 AM, Richard Biener wrote:
> On Tue, 14 Mar 2017, Martin Liška wrote:
>
>> On 03/14/2017 09:13 AM, Richard Biener wrote:
>>> On Tue, 14 Mar 2017, Martin Liška wrote:
>>>
On 03/13/2017 04:16 PM, Richard Biener wrote:
> On Mon, 13 Mar 2017, Martin Liška wrote:
>
>
On 11 March 2017 11:28:46 CET, Roland Illig wrote:
>Am 10.03.2017 um 05:12 schrieb Martin Sebor:
>> I have just an observation/question here for future consideration.
>> If this sort of diagnostic is common (I count 23 instances of it)
>> or if it is expected to become common, would it make sense
On 03/14/2017 10:46 AM, Richard Biener wrote:
> On Mon, Mar 13, 2017 at 4:19 PM, Martin Liška wrote:
>> Hello.
>>
>> This is a small follow-up patch, where local.local flag should be also
>> dropped
>> for a default implementation.
>>
>> Patch can bootstrap on x86_64-linux-gnu and survives regres
On Tue, 14 Mar 2017, Martin Liška wrote:
> On 03/14/2017 10:12 AM, Richard Biener wrote:
> > On Tue, 14 Mar 2017, Martin Liška wrote:
> >
> >> On 03/14/2017 09:13 AM, Richard Biener wrote:
> >>> On Tue, 14 Mar 2017, Martin Liška wrote:
> >>>
> On 03/13/2017 04:16 PM, Richard Biener wrote:
>
On 03/14/2017 11:13 AM, Richard Biener wrote:
> On Tue, 14 Mar 2017, Martin Liška wrote:
>
>> On 03/14/2017 10:12 AM, Richard Biener wrote:
>>> On Tue, 14 Mar 2017, Martin Liška wrote:
>>>
On 03/14/2017 09:13 AM, Richard Biener wrote:
> On Tue, 14 Mar 2017, Martin Liška wrote:
>
>
Thanks for review,
> Skimming over the patch I noticed you duplicate libiberties xcrc32
> functionality.
should i take care about standalone libbacktrace ?
https://github.com/ianlancetaylor/libbacktrace
> Also the additions to posix.c probably belong to dwarf.c and elf.c
(the feature
> is dwa
Hello.
This fixes ICE when one does not provide valid target names:
__attribute__((target_clones("default,foo,bar")))
In that situation I suggest to print:
$ ./xgcc -B. /tmp/mvc-ice.c
/tmp/mvc-ice.c:6:1: error: attribute(target("foo")) is unknown
foo ()
^~~
/tmp/mvc-ice.c:6:1: error: attribute
On Tue, Mar 14, 2017 at 11:09 AM, Martin Liška wrote:
> On 03/14/2017 10:46 AM, Richard Biener wrote:
>> On Mon, Mar 13, 2017 at 4:19 PM, Martin Liška wrote:
>>> Hello.
>>>
>>> This is a small follow-up patch, where local.local flag should be also
>>> dropped
>>> for a default implementation.
>>
On Tue, 14 Mar 2017, Martin Liška wrote:
> On 03/14/2017 11:13 AM, Richard Biener wrote:
> > On Tue, 14 Mar 2017, Martin Liška wrote:
> >
> >> On 03/14/2017 10:12 AM, Richard Biener wrote:
> >>> On Tue, 14 Mar 2017, Martin Liška wrote:
> >>>
> On 03/14/2017 09:13 AM, Richard Biener wrote:
>
On 03/14/2017 11:30 AM, Richard Biener wrote:
> On Tue, 14 Mar 2017, Martin Liška wrote:
>
>> On 03/14/2017 11:13 AM, Richard Biener wrote:
>>> On Tue, 14 Mar 2017, Martin Liška wrote:
>>>
On 03/14/2017 10:12 AM, Richard Biener wrote:
> On Tue, 14 Mar 2017, Martin Liška wrote:
>
>
On Tue, 14 Mar 2017, Martin Liška wrote:
> On 03/14/2017 11:30 AM, Richard Biener wrote:
> > On Tue, 14 Mar 2017, Martin Liška wrote:
> >
> >> On 03/14/2017 11:13 AM, Richard Biener wrote:
> >>> On Tue, 14 Mar 2017, Martin Liška wrote:
> >>>
> On 03/14/2017 10:12 AM, Richard Biener wrote:
>
On 03/14/2017 11:29 AM, Richard Biener wrote:
> On Tue, Mar 14, 2017 at 11:09 AM, Martin Liška wrote:
>> On 03/14/2017 10:46 AM, Richard Biener wrote:
>>> On Mon, Mar 13, 2017 at 4:19 PM, Martin Liška wrote:
Hello.
This is a small follow-up patch, where local.local flag should be a
On Mon, Mar 13, 2017 at 9:26 AM, marxin wrote:
> gcc/ChangeLog:
Ok.
Richard.
> 2017-03-13 Martin Liska
>
> * multiple_target.c (create_dispatcher_calls): Check that
> a target can create a function dispatcher.
> ---
> gcc/multiple_target.c | 7 +++
> 1 file changed, 7 in
On Tue, Mar 14, 2017 at 11:24 AM, Martin Liška wrote:
> Hello.
>
> This fixes ICE when one does not provide valid target names:
> __attribute__((target_clones("default,foo,bar")))
>
> In that situation I suggest to print:
>
> $ ./xgcc -B. /tmp/mvc-ice.c
> /tmp/mvc-ice.c:6:1: error: attribute(targe
On Tue, Mar 14, 2017 at 12:04 PM, Martin Liška wrote:
> On 03/14/2017 11:29 AM, Richard Biener wrote:
>> On Tue, Mar 14, 2017 at 11:09 AM, Martin Liška wrote:
>>> On 03/14/2017 10:46 AM, Richard Biener wrote:
On Mon, Mar 13, 2017 at 4:19 PM, Martin Liška wrote:
> Hello.
>
> This
On 03/14/2017 11:48 AM, Richard Biener wrote:
> On Tue, 14 Mar 2017, Martin Liška wrote:
>
>> On 03/14/2017 11:30 AM, Richard Biener wrote:
>>> On Tue, 14 Mar 2017, Martin Liška wrote:
>>>
On 03/14/2017 11:13 AM, Richard Biener wrote:
> On Tue, 14 Mar 2017, Martin Liška wrote:
>
>
On 03/14/2017 12:55 PM, Martin Liška wrote:
> On 03/14/2017 11:48 AM, Richard Biener wrote:
>> On Tue, 14 Mar 2017, Martin Liška wrote:
>>
>>> On 03/14/2017 11:30 AM, Richard Biener wrote:
On Tue, 14 Mar 2017, Martin Liška wrote:
> On 03/14/2017 11:13 AM, Richard Biener wrote:
>>
On 03/14/2017 12:09 PM, Richard Biener wrote:
> On Tue, Mar 14, 2017 at 11:24 AM, Martin Liška wrote:
>> Hello.
>>
>> This fixes ICE when one does not provide valid target names:
>> __attribute__((target_clones("default,foo,bar")))
>>
>> In that situation I suggest to print:
>>
>> $ ./xgcc -B. /tm
Hello,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79542 reports an ICE in
dwarf2out.c for an Ada testcase built with optimization.
This crash happens during the late generation pass because
add_gnat_descriptive_type cannot find the type DIE corresponding to some
descriptive type after having tr
Status
==
The trunk is in regression and documentation fixes mode (Stage 4)
thus as if it were a release branch. We are feature complete since
quite a while and just chasing down P1 bugs which block the release
of GCC 7.
Tentative release date is mid April which means, given past history,
a
Tested on my local machine that's properly installed.
Ready for trunk?
Thanks,
Martin
>From 553c8402f8b0c77a30f4476918de1e4acff34dbc Mon Sep 17 00:00:00 2001
From: marxin
Date: Tue, 14 Mar 2017 13:26:49 +0100
Subject: [PATCH] Install gcov-dump.
gcc/ChangeLog:
2017-03-14 Martin Liska
* Make
On Tue, 14 Mar 2017, Martin Liška wrote:
> On 03/14/2017 11:48 AM, Richard Biener wrote:
> > On Tue, 14 Mar 2017, Martin Liška wrote:
> >
> >> On 03/14/2017 11:30 AM, Richard Biener wrote:
> >>> On Tue, 14 Mar 2017, Martin Liška wrote:
> >>>
> On 03/14/2017 11:13 AM, Richard Biener wrote:
>
On Tue, 14 Mar 2017, Richard Biener wrote:
> On Tue, 14 Mar 2017, Martin Liška wrote:
> >
> > /tmp/gcov-1.gcno: block
> > 2:`/home/marxin/Programming/gcc/gcc/testsuite/gcc.misc-tests/gcov-1.c':10,
> > 14
> > /tmp/gcov-1.gcno: block
> > 4:`/home/marxin/Programming/gcc/gcc/testsuite/gcc.misc
On 03/14/2017 01:33 PM, Richard Biener wrote:
> On Tue, 14 Mar 2017, Martin Liška wrote:
>
>> On 03/14/2017 11:48 AM, Richard Biener wrote:
>>> On Tue, 14 Mar 2017, Martin Liška wrote:
>>>
On 03/14/2017 11:30 AM, Richard Biener wrote:
> On Tue, 14 Mar 2017, Martin Liška wrote:
>
>
> On Mar 14, 2017, at 3:57 AM, Richard Biener
> wrote:
>
> On Tue, Mar 14, 2017 at 1:04 AM, Bill Schmidt
> wrote:
>>
>> Index: gcc/tree-stdarg.c
>> ===
>> --- gcc/tree-stdarg.c (revision 246109)
>> +++ gcc/tree-stdarg.c (work
On Tue, Mar 14, 2017 at 3:20 AM, Denis Khalikov
wrote:
> Thanks for review,
>
>> Skimming over the patch I noticed you duplicate libiberties xcrc32
>> functionality.
>
> should i take care about standalone libbacktrace ?
> https://github.com/ianlancetaylor/libbacktrace
No, don't worry about it.
Ok, thanks,
i will change patch to use crc32 from libiberty and
also implement searching for debuginfo with build id.
As it was implemented to binutils PR binutils/20876.
On 03/14/2017 04:21 PM, Ian Lance Taylor wrote:
On Tue, Mar 14, 2017 at 3:20 AM, Denis Khalikov
wrote:
Thanks for review,
On Tue, Mar 14, 2017 at 1:24 PM, Martin Liška wrote:
> On 03/14/2017 12:09 PM, Richard Biener wrote:
>> On Tue, Mar 14, 2017 at 11:24 AM, Martin Liška wrote:
>>> Hello.
>>>
>>> This fixes ICE when one does not provide valid target names:
>>> __attribute__((target_clones("default,foo,bar")))
>>>
>
On Mon, Mar 13, 2017 at 10:16 AM, Denis Khalikov
wrote:
> Hello everyone, i have a patch for this issue.
>
> List of implemented functionality:
>
> 1.Reading .gnu_debuglink section from ELF file:
> a. Reading name of debug info file.
> b. Verifying crc32 sum.
>
> 2. Searching for separate debug
On 07/02/17 14:49, Kyrill Tkachov wrote:
On 18/01/17 09:49, Kyrill Tkachov wrote:
On 19/12/16 14:53, Jakub Jelinek wrote:
On Thu, Dec 15, 2016 at 10:00:14AM +, Richard Earnshaw (lists) wrote:
sorry, pasted the wrong bit of code.
That should read when we generate:
(insn 55 19 67 3 (par
On Mon, 13 Mar 2017, Joseph Myers wrote:
> I think that as far as possible we should just use "@node node-name"
> without any of the subsequent arguments pointing to other nodes.
Thanks, Joseph.
I went ahead and applied the patch below.
Gerald
2017-03-13 Gerald Pfeifer
* doc/gcc.t
On 03/14/2017 11:48 AM, Richard Biener wrote:
> On Tue, 14 Mar 2017, Martin Liška wrote:
>
>> On 03/14/2017 11:30 AM, Richard Biener wrote:
>>> On Tue, 14 Mar 2017, Martin Liška wrote:
>>>
On 03/14/2017 11:13 AM, Richard Biener wrote:
> On Tue, 14 Mar 2017, Martin Liška wrote:
>
>
On Tue, Mar 14, 2017 at 1:30 PM, Martin Liška wrote:
> Tested on my local machine that's properly installed.
>
> Ready for trunk?
Ok.
Richard.
> Thanks,
> Martin
On Tue, 14 Mar 2017, Martin Liška wrote:
> On 03/14/2017 11:48 AM, Richard Biener wrote:
> > On Tue, 14 Mar 2017, Martin Liška wrote:
> >
> >> On 03/14/2017 11:30 AM, Richard Biener wrote:
> >>> On Tue, 14 Mar 2017, Martin Liška wrote:
> >>>
> On 03/14/2017 11:13 AM, Richard Biener wrote:
>
> On Mar 14, 2017, at 7:50 AM, Bill Schmidt wrote:
>
>
>> On Mar 14, 2017, at 3:57 AM, Richard Biener
>> wrote:
>>
>> On Tue, Mar 14, 2017 at 1:04 AM, Bill Schmidt
>> wrote:
>>>
>>> Index: gcc/tree-stdarg.c
>>> ===
>>> --- gcc
On Tue, Mar 14, 2017 at 3:20 PM, Bill Schmidt
wrote:
>
>> On Mar 14, 2017, at 7:50 AM, Bill Schmidt
>> wrote:
>>
>>
>>> On Mar 14, 2017, at 3:57 AM, Richard Biener
>>> wrote:
>>>
>>> On Tue, Mar 14, 2017 at 1:04 AM, Bill Schmidt
>>> wrote:
Index: gcc/tree-stdarg.c
=
Thanks for review, got all of my mistakes, except one.
> - descriptor = backtrace_open (info->dlpi_name, pd->error_callback,
> - pd->data, &does_not_exist);
> + descriptor
> + = backtrace_open_debugfile (info->dlpi_name, pd->error_callback,
pd->data,
> +&debugfile_does_not_exis
> On Mar 14, 2017, at 9:25 AM, Richard Biener
> wrote:
>
> On Tue, Mar 14, 2017 at 3:20 PM, Bill Schmidt
> wrote:
>>
>>> On Mar 14, 2017, at 7:50 AM, Bill Schmidt
>>> wrote:
>>>
>>>
On Mar 14, 2017, at 3:57 AM, Richard Biener
wrote:
On Tue, Mar 14, 2017 at 1:04 AM,
On 03/13/2017 06:20 PM, Nathan Sidwell wrote:
On 03/13/2017 05:05 PM, Jason Merrill wrote:
It looks like you're ignoring the access for all base destructors;
handling this in synthesized_method_base_walk would let you limit the
change to vbases with virtual destructors. That function also alre
This showed up in power9 code for __divkf3 software float support and
caused a divd to be emitted where we needed a divdu.
backported/bootstrapped/regtested to gcc-6-branch
Index: gcc/config/rs6000/rs6000.md
===
--- gcc/config/rs6000
This fixes a new ambiguity in C++17 mode introduced by string_view
support in basic_string.
PR libstdc++/79162
* include/bits/basic_string.h [_GLIBCXX_USE_CXX11_ABI]
(basic_string::operator=(basic_string_view)): Replace
with a constrained template.
[!_GLIBC
Hello.
This is small documentation patch that lists and briefly describes -Wchkp.
Martin
>From 553e0c83a1b1efbaff7666f5ab7303e816b958d4 Mon Sep 17 00:00:00 2001
From: marxin
Date: Tue, 14 Mar 2017 15:41:47 +0100
Subject: [PATCH] Document -Wchkp (PR middle-end/79831).
gcc/ChangeLog:
2017-03-14
Hello.
This mentions all options that can't be combined with -fcheck-pointer-bounds.
Thanks,
Martin
>From 78e199c5f0359de1c74cf44aaa8947a0ae950dd3 Mon Sep 17 00:00:00 2001
From: marxin
Date: Tue, 14 Mar 2017 16:00:03 +0100
Subject: [PATCH] Document options that can't be combined with
-fcheck-po
On 03/14/2017 09:02 AM, Martin Liška wrote:
Hello.
This mentions all options that can't be combined with -fcheck-pointer-bounds.
OK.
jeff
On 03/14/2017 09:01 AM, Martin Liška wrote:
Hello.
This is small documentation patch that lists and briefly describes -Wchkp.
OK.
jeff
On 03/14/2017 03:01 AM, Richard Biener wrote:
On Tue, Mar 14, 2017 at 1:37 AM, Martin Sebor wrote:
Ping: this a P3 regression targeted at 7.0.1. It was found
on x86_64-apple-darwin10.8.0 but affects all targets (even
if it doesn't happen to manifest on them):
https://gcc.gnu.org/ml/gcc-patc
On Tue, Mar 14, 2017 at 10:43 AM, Nathan Sidwell wrote:
> On 03/13/2017 06:20 PM, Nathan Sidwell wrote:
>>
>> On 03/13/2017 05:05 PM, Jason Merrill wrote:
>>
>>> It looks like you're ignoring the access for all base destructors;
>>> handling this in synthesized_method_base_walk would let you limit
On Mar 14, 2017, at 9:32 AM, Bill Schmidt wrote:
>
>> On Mar 14, 2017, at 9:25 AM, Richard Biener
>> wrote:
>>
> Better is sth like
>
> Index: gcc/tree-stdarg.c
> ===
> --- gcc/tree-stdarg.c (revision 246082
I've backported the attached patches gcc-6.
Marek
Bootstrapped/regtested on x86_64-linux, ok for trunk?
2017-03-14 Marek Polacek
PR c++/79962
PR c++/79984
* c-common.c (handle_nonnull_attribute): Save the result of default
conversion to the attribute li
On Tue, Mar 14, 2017 at 7:30 AM, Denis Khalikov
wrote:
> Thanks for review, got all of my mistakes, except one.
>
>
>> - descriptor = backtrace_open (info->dlpi_name, pd->error_callback,
>> - pd->data, &does_not_exist);
>> + descriptor
>> + = backtrace_open_debugfile (info->dlpi_name,
On 03/13/2017 04:34 PM, Bruce Korb wrote:
On 03/13/17 15:02, Gerald Pfeifer wrote:
On Mon, 13 Mar 2017, Joseph Myers wrote:
I am currently translating GCC into German. During that, I noticed that
in some places the term "zero character" means '\0'. The official term
though is "null character",
On 14.03.2017 15:15, Richard Biener wrote:
> On Tue, Mar 14, 2017 at 1:30 PM, Martin Liška wrote:
>> Tested on my local machine that's properly installed.
>>
>> Ready for trunk?
>
> Ok.
>
> Richard.
shouldn't that go to the active branches as well?
Matthias
On 03/06/2017 01:27 AM, Xi Ruoyao wrote:
Hi,
After Bernd fixed PR44281 (r235809), the registers fixed only because
they are global can be selected by IRA. However, since they are not
in ok_regs, the move cost estimation about them are wrong. Then an
assertion in ira.c failed and then ICE.
To fi
On 03/03/2017 06:51 AM, Bernd Schmidt wrote:
This is an ICE where setup_pressure_classes fails if xmm0 is a global
reg. Instead of GENERAL/FLOAT/SSE/MMX_REGS, it computes only
SSE_FIRST_REG as the third register class. The problem is that the costs
for moving between SSE_FIRST_REG and SSE_REGS ar
Thanks for answer, i got it now.
I will also delete all readlink code. Looks like is no reason
to use it instead just one call of realpath(char*,char*). Binutils
using realpath in the same cases.
On 03/14/2017 07:26 PM, Ian Lance Taylor wrote:
On Tue, Mar 14, 2017 at 7:30 AM, Denis Khalikov
wro
On 03/03/2017 06:51 AM, Bernd Schmidt wrote:
This is an ICE where setup_pressure_classes fails if xmm0 is a global
reg. Instead of GENERAL/FLOAT/SSE/MMX_REGS, it computes only
SSE_FIRST_REG as the third register class. The problem is that the costs
for moving between SSE_FIRST_REG and SSE_REGS ar
On Tue, Mar 7, 2017 at 12:10 PM, Marek Polacek wrote:
> In this testcase we have
> C c = bar (X{1});
> which store_init_value sees as
> c = TARGET_EXPR .n=(&)->i}>)>
> i.e. we're initializing "c" with a TARGET_EXPR. We call replace_placeholders
> that walks the whole tree to substitute the place
On Tue, Mar 14, 2017 at 2:33 PM, Jason Merrill wrote:
> On Tue, Mar 7, 2017 at 12:10 PM, Marek Polacek wrote:
>> In this testcase we have
>> C c = bar (X{1});
>> which store_init_value sees as
>> c = TARGET_EXPR > .n=(&)->i}>)>
>> i.e. we're initializing "c" with a TARGET_EXPR. We call replace_p
On 13/03/17 19:35 +, Jonathan Wakely wrote:
This is a series of patches to fix various bugs in the Unicode
character conversion facets.
Ther first patch fixes a silly < versus <= bug that meant that 0x
got written as a surrogate pair instead of as simply 0xff, and an
endianness bug for t
In formal writing it's recommended to prefer the word "cannot"
to the somewhat informal "can't."
The GCC manual uses "cannot" in most places (280 lines) but there
are a few instances of "can't" (33 lines).
The attached patch replaces the informal "can't" with the former
for consistency.
Thanks
On 03/12/2017 07:32 PM, Martin Sebor wrote:
On 03/10/2017 10:51 PM, Jeff Law wrote:
On 03/10/2017 09:20 AM, Martin Sebor wrote:
On 03/10/2017 05:57 AM, Rainer Orth wrote:
Hi Segher,
On Fri, Feb 10, 2017 at 11:56:39AM +0100, Rainer Orth wrote:
Segher Boessenkool writes:
As stated in the P
Martin Sebor writes:
> @@ -373,7 +373,7 @@ example, this code would produce an error:
>
> @smallexample
> #if 0
> -You can't expect this to work.
> +You cannot expect this to work.
> #endif
> @end smallexample
>
Sure the maintainers would have caught this, but: the "'" is needed here.
The
On 03/12/2017 05:23 PM, Gerald Pfeifer wrote:
Hi Martin,
On Mon, 27 Feb 2017, Martin Sebor wrote:
Sorry to be jumping in so late. I only noticed this bit now.
I would suggest to say that these new built-ins evaluate to integer
constant expressions when their arguments do. Not all C programmer
Hello everyone,
a simple patch to throw a warning if not all and not none of the
equivalence objects are volatile. (And the according modification of
gfortran.dg/volatile11.f90)
Nicolas
Regression tested for:
GNU Fortran (GCC) 7.0.1 20170311 (experimental)
Changelog:
2017-03-13 Nicolas K
Segher confirmed that power.org is gone and that it's okay to remove
those links for now.
He kindly agreed to help and look for alternatives.
Applied.
Gerald
Index: readings.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/readings.html,
niXman 2017-02-12 20:28:
Hi,
Tested on i686/x86_64-MinGW-W64
Please test possible regressions on posix platform.
As continuation for:
https://gcc.gnu.org/ml/libstdc++/2017-02/msg00041.html
Regression on posix platform was fixed.
Tested on i686/x86_64-MinGW-W64 and x86_64-linux-gnu.
Index
> The GCC manual uses "cannot" in most places (280 lines) but there
> are a few instances of "can't" (33 lines).
>
> The attached patch replaces the informal "can't" with the former
> for consistency.
In my opinion, this is the wrong direction. Contractions are becoming
more acceptable in even m
In PR target/79947, the code for using the float reciprocal square root
estimate instruction did not check if the -mpowerpc-gfxopt option was enabled.
The code needs this option to generate a conditional floating point move.
I have checked this patch on the trunk, and it fixes the problem and it d
This patch corrects several errors in a patch that was submitted on
2017-03-01. A copy-and-paste error in the previous patch resulted in
accidental use of the lt flag instead of the eq flag to represent the
outcome of the vec_any_eq built-in function. Also, in reviewing the
code of the previous
> On Mar 14, 2017, at 11:07 AM, Bill Schmidt
> wrote:
>>
>> Your suggestion failed bootstrap in libiberty on vprintf-support.c.
>> Compilation failed with:
>>
>> /home/wschmidt/gcc/build/gcc-mainline-test2-debug/gcc/xgcc
>> -B/home/wschmidt/gcc/build/gcc-mainline-test2-debug/gcc/
>> -B/hom
On 03/14/2017 01:17 PM, Nicolas Koenig wrote:
> Hello everyone,
>
> a simple patch to throw a warning if not all and not none of the equivalence
> objects are volatile. (And the according modification of
> gfortran.dg/volatile11.f90)
>
> Nicolas
>
> Regression tested for:
>
> GNU Fortran (GCC)
On 03/13/2017 02:44 AM, Richard Biener wrote:
On Mon, Mar 13, 2017 at 2:13 AM, Martin Sebor wrote:
r243470 decorates standard allocation functions like alloca
and malloc with attribute alloc_size. However, in applying
the attribute to aligned_alloc I had overlooked that the size
argument is th
On 03/07/2017 06:03 PM, Martin Sebor wrote:
In bug 79936 - ICE with -Walloc-size-larger-than=32767 the reporter
encountered an ICE on x86_64-apple-darwin10.8.0 caused by GCC source
file that implements the warning accessing a global tree without
having included the file in GTFILES make variable.
Hi Mike,
On Tue, Mar 14, 2017 at 05:01:53PM -0400, Michael Meissner wrote:
> In PR target/79947, the code for using the float reciprocal square root
> estimate instruction did not check if the -mpowerpc-gfxopt option was enabled.
> The code needs this option to generate a conditional floating poin
2017-03-10 16:15 GMT+03:00 Martin Liška :
> Hello.
>
> Currently, __builtin_ia32_bndret is used for all functions that have non-void
> return type. I think the right fix is to return bounds just for a bounded
> type.
>
> Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
>
> Re
I noticed that gcc/fortran/trans-stmt.h made a reference to a
non-existent trans-openacc.c. Those functions have been placed in
trans-openmp.c. This patch has been applied to gomp-4_0-branch to
correct that error.
Cesar
2017-03-14 Cesar Philippidis
gcc/fortran/
* trans-stmt.h: Remove stale r
On 03/14/2017 01:41 PM, Richard Sandiford wrote:
Martin Sebor writes:
@@ -373,7 +373,7 @@ example, this code would produce an error:
@smallexample
#if 0
-You can't expect this to work.
+You cannot expect this to work.
#endif
@end smallexample
Sure the maintainers would have caught this,
On Tue, 14 Mar 2017, Martin Sebor wrote:
> PS I wasted quite a bit of time updating tm.texi. I kept getting
> the error below and didn't realize (forgot) that it was asking me
> to copy $objdir/gcc/tm.texi to $srcdir/gcc/doc/tm.texi. Can
> someone explain why this file requires these special ste
On 03/14/2017 10:42 PM, Jerry DeLisle wrote:
On 03/14/2017 01:17 PM, Nicolas Koenig wrote:
Hello everyone,
a simple patch to throw a warning if not all and not none of the equivalence
objects are volatile. (And the according modification of
gfortran.dg/volatile11.f90)
Nicolas
Regression tes
Hello world,
well, here is the third attempt at fixing the second part of the PR.
Glancing over the source, I think there are quite a few places where
we currently issue a runtime error which we could replace by an
assert, but that's something for 8.0.
Regression-tested on x86_64-pc-linux-gnu.
On 03/10/2017 04:24 PM, Bernd Schmidt wrote:
In this PR, we have a few insns involved in two instruction combinations:
insn 16: set r100
insn 27: some calculation
insn 28: some calculation
insn 32: using r100
insn 33: using r100
insn 35: some calculation
Then we combine insns 27, 28 and 33, pro
On 03/15/2017 12:03 AM, Jeff Law wrote:
On 03/10/2017 04:24 PM, Bernd Schmidt wrote:
PR rtl-optimization/79910
* combine.c (record_used_regs): New static function.
(try_combine): Handle situations where there is an additional
instruction between I2 and I3 which needs to have a L
On 10/03/17 15:20 +, Jonathan Wakely wrote:
On 09/03/17 19:46 +, Jonathan Wakely wrote:
On 03/03/17 10:47 -0500, David Edelsohn wrote:
This patch caused a new regression on AIX.
I'm unable to bootstrap on either gcc111 or gcc119 so I can't test
the fix.
export CONFIG_SHELL=/usr/bin/
This triggered a kernel miscompilation with an old (4.8 I think) aarch64
toolchain.
Here's the reloads for the insn where things go wrong:
Reloads for insn # 210
Reload 0: reload_in (DI) = (reg/v/f:DI 80 [ pgdata ])
GENERAL_REGS, RELOAD_FOR_INPUT_ADDRESS (opnum = 0)
reload_in_re
On Tue, Mar 14, 2017 at 4:22 PM, Bernd Schmidt wrote:
> This triggered a kernel miscompilation with an old (4.8 I think) aarch64
> toolchain.
Yes RHEL's 4.8 has the issue. So did Cavium/MontaVista's GCC 4.7 with
AARCH64 support backported to it. We would work around the bug in the
kernel some o
1 - 100 of 112 matches
Mail list logo