[vrp] use get_ptr_nonnull in tree-vrp

Hi, This patch uses get_ptr_nonnull in tree-vrp. Bootstrapped and regression tested this with other patched without any new regressions on x86_64-linux-gnu. Is this OK for trunk? Thanks, Kugan gcc/testsuite/ChangeLog: 2016-10-12 Kugan Vivekanandarajah * gcc.dg/ipa/vrp4.c: Adjust

[ipa-vrp] Use get/set_ptr_nonnull in ipa-vrp

Hi, This patch uses the get/set_ptr_nonnull so that ipa-vrp also propagates nonnull ranges for pinter. Bootstrapped and regression tested this with other patched without any new regressions on x86_64-linux-gnu. Is this OK for trunk? Thanks, Kugan gcc/ChangeLog: 2016-10-12 Kugan Vivek

Re: Set nonnull attribute to ptr_info_def based on VRP

Hi Richard, On 07/10/16 21:03, Richard Biener wrote: On Fri, Oct 7, 2016 at 2:53 AM, kugan wrote: Hi Richard, Thanks for the review. On 09/08/16 18:58, Richard Biener wrote: On Tue, Aug 9, 2016 at 12:58 AM, kugan wrote: Hi Jakub, Thanks for the review. On 08/08/16 16:40, Jakub Jelin

Re: [RFC][VRP] Improve intersect_ranges

Hi Richard, On 12/10/16 00:14, Richard Biener wrote: On Tue, Oct 11, 2016 at 2:57 AM, kugan wrote: Hi Richard, Hi Richard, On 10/10/16 20:13, Richard Biener wrote: On Sat, Oct 8, 2016 at 9:38 PM, kugan wrote: Hi Richard, Thanks for the review. On 07/10/16 20:11, Richard Biener wrote:

Re: [PATCH] Fix optimize_range_tests_var_bound reassoc ICE (PR tree-optimization/77929)

On October 11, 2016 11:59:23 PM GMT+02:00, Jakub Jelinek wrote: >Hi! > >The following testcase ICEs, because ranges[i].exp is x < y >with boolean type, but (*ops)[ranges[i].idx] is that result cast >to int and the code didn't take into account possible casts that >init_range_entry looks through.

PING [PATCH] accept flexible arrays in struct in unions (c++/71912 - [6/7 regression])

Jason, Are there any other changes you want me to make to the patch? I leave this weekend for the WG14 meeting and would like to get this change finalized and hopefully committed before then. https://gcc.gnu.org/ml/gcc-patches/2016-10/msg00410.html Thanks Martin On 10/06/2016 02:29 PM, Marti

Re: [PATCH] Introduce -Wimplicit-fallthrough={0,1,2,3,4,5}

On 10/12/2016 01:12 AM, Jakub Jelinek wrote: What I perhaps should try is removing the Common keyword from the Wimplicit-fallthrough and Wimplicit-fallthrough= entries, e.g. similarly to how Wnonnull-compare is defined just as Var(...) Warning in common.opt (so that it can be used in the middle-e

Re: [PATCH] Introduce -Wimplicit-fallthrough={0,1,2,3,4,5}

On Wed, Oct 12, 2016 at 12:52:49AM +0200, Bernd Schmidt wrote: > On 10/12/2016 12:34 AM, Bernd Schmidt wrote: > > >>* c.opt (Wextra): Add as C/C++/ObjC/ObjC++ option. > >>(Wimplicit-fallthrough=): Enable for these languages by -Wextra. > > > >This bit looks like it does a bit more magic th

Re: [PATCH] Introduce -Wimplicit-fallthrough={0,1,2,3,4,5}

On Wed, Oct 12, 2016 at 12:34:45AM +0200, Bernd Schmidt wrote: > On 10/11/2016 11:52 PM, Jakub Jelinek wrote: > >The following patch introduces difference warning levels for > >-Wimplicit-fallthrough warning, so projects can choose if they want to > >honor only attributes (-Wimplicit-fallthrough=5)

Re: [PATCH] Introduce -Wimplicit-fallthrough={0,1,2,3,4,5}

On 10/12/2016 12:34 AM, Bernd Schmidt wrote: * c.opt (Wextra): Add as C/C++/ObjC/ObjC++ option. (Wimplicit-fallthrough=): Enable for these languages by -Wextra. This bit looks like it does a bit more magic than is immediately obvious. Could you elaborate how this works? Ok, so it loo

Re: [PATCH] Introduce -Wimplicit-fallthrough={0,1,2,3,4,5}

On 10/11/2016 11:52 PM, Jakub Jelinek wrote: The following patch introduces difference warning levels for -Wimplicit-fallthrough warning, so projects can choose if they want to honor only attributes (-Wimplicit-fallthrough=5), or what kind of comments. =4 is very picky and accepts only very small

Re: [SPARC] Tidy up Condition Code support and more

> Note that the ADDXC, ADDXCCC, SUBXC and SUBXCCC instructions do not > support immediate operands. Hence the patch breaks vis3-enabling arches > and niagara-7. Egad. I totally overlooked this (yet the -mcpu=niagara7 -m64 testsuite is rather explicit) and this is a bit of a shame, especially fo

[PATCH] Fix optimize_range_tests_var_bound reassoc ICE (PR tree-optimization/77929)

Hi! The following testcase ICEs, because ranges[i].exp is x < y with boolean type, but (*ops)[ranges[i].idx] is that result cast to int and the code didn't take into account possible casts that init_range_entry looks through. Fixed thusly, bootstrapped/regtested on x86_64-linux and i686-linux, ok

[PATCH] Introduce -Wimplicit-fallthrough={0,1,2,3,4,5}

Hi! The following patch introduces difference warning levels for -Wimplicit-fallthrough warning, so projects can choose if they want to honor only attributes (-Wimplicit-fallthrough=5), or what kind of comments. =4 is very picky and accepts only very small amount of comments, =3 is what we had bef

ping for msg00567

Hi, A few days ago I sent a patch to libstdc++-v3[1], but the patch is still not applied. Why? Moreover, when I try to ping this thread my messages are returned to sender. Why? [1] https://gcc.gnu.org/ml/gcc-patches/2016-10/msg00567.html -- Regards, niXman __

[Committed] PR fortran/77942 -- test for zero

Committed to 6-branch and trunk. 2016-10-11 Steven G. Kargl PR fortran/77942 * simplify.c (gfc_simplify_cshift): Check for zero. 2016-10-11 Steven G. Kargl PR fortran/77942 * gfortran.dg/pr77942.f90 Index: gcc/fortran/simplify.c ==

[PR tree-optimization/77424] Cleanup remnants of threading through backedges in old threader

As Jon pointed out in the BZ, there's an if-else in tree-ssa-threadupdate.c where the if and else blocks are equivalent. Clearly that's all that useful. The code in question used to be an if-elseif-else construct where the elseif block did something different. The elseif block was removed w

gcc-patches@gcc.gnu.org

On Tue, 11 Oct 2016, Bin Cheng wrote: We missed folding (convert)(X op const) -> (convert)X op (convert)const for unsigned narrowing because of reason reported at https://gcc.gnu.org/ml/gcc/2016-07/msg00126.html This patch fixes the issue by adding new match&simplify pattern, it also adds a t

Re: [PATCH v4 0/6] Separate shrink-wrapping

On 10/03/2016 07:48 AM, Segher Boessenkool wrote: I updated according to Jeff's latest comments (importantly, we cannot move a *logue in front of a move in general), and added some testcases. Bootstrapping is in progress on today's trunk, powerpc64-linux and powerpc64le-linux. Is this okay to c

Re: [PATCH,rs6000] Add built-in function support for Power9 string operations

Index: gcc/doc/extend.texi === --- gcc/doc/extend.texi (revision 239612) +++ gcc/doc/extend.texi (working copy) @@ -15019,6 +15019,139 @@ The @code{__builtin_dfp_dtstsfi_ov_dd} and require that the type of the @code{value} argument b

Re: [PATCH] Implement new hook for max_align_t_align

On Tue, Oct 11, 2016 at 4:54 PM, John David Anglin wrote: > On 2016-10-11 4:11 PM, Jason Merrill wrote: >> >> On Tue, Oct 11, 2016 at 2:59 PM, DJ Delorie wrote: >>> >>> Jason Merrill writes: If PA malloc doesn't actually provide 16-byte alignment, this change seems problematic; it

Re: [patch] Fix ICE on ACATS test for Aarch64 at -O

> Revised patch attached, tested on x86-64/Linux, OK for the mainline? Also tested on Aarch64/Linux, where it cleans up the ACATS testsuite: --- mail-report.log.0 2016-10-11 04:01:06.020972999 -0700 +++ mail-report.log 2016-10-11 14:27:42.110972999 -0700 @@ -2,12 +2,10 @@ LAST_UPDATED: Obt

Re: [PATCH] Implement new hook for max_align_t_align

On Tue, Oct 11, 2016 at 04:54:56PM -0400, John David Anglin wrote: > But the check isn't directly about malloc. It's between the alignment for > max_align_t > and the alignment that the type wants. Joseph indicated that max_align_t > should have an > alignment as large as the POSIX types (e.g., p

Re: [PATCH] Implement new hook for max_align_t_align

On 2016-10-11 4:11 PM, Jason Merrill wrote: On Tue, Oct 11, 2016 at 2:59 PM, DJ Delorie wrote: Jason Merrill writes: If PA malloc doesn't actually provide 16-byte alignment, this change seems problematic; it will mean any type that wants 16-byte alignment will silently get 8-byte alignment in

Re: [PATCH] Fix PR77826

On Tue, 11 Oct 2016, Richard Biener wrote: An example that regressed at -O (looking at the .optimized dump) int f(int a, unsigned b){ a &= 1; b &= 1; return a&b; } Yeah, but it usually also shows a badly written pattern: /* (X & Y) & (X & Z) -> (X & Y) & Z (X | Y) | (X | Z) -> (X | Y

Re: New option -flimit-function-alignment

On 10/11/2016 04:23 PM, Denys Vlasenko wrote: This is better than current behavior, but this is not what I want. 15-byte function does not need to be aligned to 16 bytes on a machine with 128-byte L1I cachelines. It needs to be aligned to 128 bytes if there are less than 15 bytes remaining; if

Re: fix -fmax-errors & notes

On 10/11/16 16:07, David Malcolm wrote: This logic is running when the next diagnostic is about to be emitted. But what if the user has selected -Wfatal-errors and there's a single error and no further diagnostics? Could this change the observable behavior? (I'm trying to think of a case here,

Re: [PATCH] Implement new hook for max_align_t_align

On Tue, Oct 11, 2016 at 2:59 PM, DJ Delorie wrote: > > Jason Merrill writes: >> If PA malloc doesn't actually provide 16-byte alignment, this change >> seems problematic; it will mean any type that wants 16-byte alignment >> will silently get 8-byte alignment instead. > > Should such cases be cal

Re: [PATCH] Fix formatting of the -fdec-math changes

On Tue, Oct 11, 2016 at 09:00:54PM +0200, Jakub Jelinek wrote: > On Tue, Oct 11, 2016 at 02:47:34PM -0400, Fritz Reese wrote: > > On Tue, Oct 11, 2016 at 2:44 PM, Fritz Reese wrote: > > > On Mon, 2016-10-11 08:43 AM, Markus Trippelsdorf > > > wrote: > > >> This patch breaks bootstrap: > > > ...

Re: fix -fmax-errors & notes

On Tue, 2016-10-11 at 06:34 -0400, Nathan Sidwell wrote: > Hi, > Jonathan & I were chatting at the cauldron about how -fmax-errors > kills any > notes about the final error. That's because we bail out just after > emitting the > final error. This patch fixes the problem by bailing out just befo

Re: [PATCH] Implement new hook for max_align_t_align

On 2016-10-11 2:50 PM, Jason Merrill wrote: /* Alignment, in bits, a C conformant malloc implementation has to provide. The HP-UX malloc implementation provides a default alignment of 8 bytes. This can be increased with mallopt. The glibc implementation also provides 8-byte alignment

[Ada] Set Backend_Overflow_Checks to True everywhere

It's not clear why this was set to False in some configuration files. Applied on the mainline. 2016-10-11 Eric Botcazou * system-linux-armeb.ads (Backend_Overflow_Checks): Change to True. * system-linux-mips.ads (Backend_Overflow_Checks): Likewise. * system-linux-mips

Re: [PATCH v2] aarch64: Add split-stack initial support

On 07/10/2016 05:28, Kyrill Tkachov wrote: > Hi Adhemerval, > > CC'ing the aarch64 maintainers/reviewers. > I have some comments inline, mostly about the GCC coding conventions. Thanks for the review. >> diff --git a/gcc/config/aarch64/aarch64.c b/gcc/config/aarch64/aarch64.c >> index df6514d.

Re: [PATCH] Fix formatting of the -fdec-math changes

On Tue, Oct 11, 2016 at 03:15:24PM -0400, Fritz Reese wrote: > > --- gcc/fortran/simplify.c.jj 2016-10-11 20:51:01.767308095 +0200 > > +++ gcc/fortran/simplify.c 2016-10-11 20:56:27.468199551 +0200 > > @@ -1717,27 +1717,24 @@ simplify_trig_call (gfc_expr *icall) > > > >/* The actual simp

Re: [PATCH][check_GNU_style.sh] More aggressively ignore dg-xxx directives

On Tue, Oct 11, 2016 at 01:11:04PM -0600, Martin Sebor wrote: > Also, the pattern that starts with "/\+\+\+" looks like it's missing > the ^ anchor. Presumably it should be "/^\+\+\+ \/testsuite\//". No, it will be almost never +++ /testsuite/ There needs to be .* in between "+++ " and "/testsuit

Re: [PATCH] Fix formatting of the -fdec-math changes

On Tue, Oct 11, 2016 at 3:00 PM, Jakub Jelinek wrote: > On Tue, Oct 11, 2016 at 02:47:34PM -0400, Fritz Reese wrote: >> On Tue, Oct 11, 2016 at 2:44 PM, Fritz Reese wrote: >> > On Mon, 2016-10-11 08:43 AM, Markus Trippelsdorf >> > wrote: >> >> This patch breaks bootstrap: >> > ... >> > >> > Sor

Re: [PATCH][check_GNU_style.sh] More aggressively ignore dg-xxx directives

On 10/11/2016 09:22 AM, Kyrill Tkachov wrote: On 11/10/16 16:13, Jeff Law wrote: On 10/11/2016 05:01 AM, Bernd Schmidt wrote: On 10/11/2016 12:56 PM, Jakub Jelinek wrote: On Tue, Oct 11, 2016 at 11:47:21AM +0100, Kyrill Tkachov wrote: check_GNU_style.sh complains a lot about dg-* directives

[PATCH] Fix formatting of the -fdec-math changes

On Tue, Oct 11, 2016 at 02:47:34PM -0400, Fritz Reese wrote: > On Tue, Oct 11, 2016 at 2:44 PM, Fritz Reese wrote: > > On Mon, 2016-10-11 08:43 AM, Markus Trippelsdorf > > wrote: > >> This patch breaks bootstrap: > > ... > > > > Sorry all!! was in a rush to get in the car this morning and made a

Re: [PATCH] Implement new hook for max_align_t_align

Jason Merrill writes: > If PA malloc doesn't actually provide 16-byte alignment, this change > seems problematic; it will mean any type that wants 16-byte alignment > will silently get 8-byte alignment instead. Should such cases be calling memalign (or posix_memalign) instead of malloc?

Re: [PATCH] Implement new hook for max_align_t_align

/* Alignment, in bits, a C conformant malloc implementation has to provide. The HP-UX malloc implementation provides a default alignment of 8 bytes. This can be increased with mallopt. The glibc implementation also provides 8-byte alignment. Note that this isn't enough for various POSIX

Bootstrap breakage in Fortran

There was a breakage in Fortran that has now been fixed. In case anyone runs into it. Resolved by: M gcc/fortran/ChangeLog M gcc/fortran/iresolve.c M gcc/fortran/simplify.c r241000 = 7b8ebc39f2db57dcadd8b8f22b6b7561d187c279 (refs/remotes/svn/trunk) Rela

Re: PING! Re: [PATCH, Fortran] Extension: COTAN and degree-valued trig intrinsics with -fdec-math

On Tue, Oct 11, 2016 at 2:44 PM, Fritz Reese wrote: > On Mon, 2016-10-11 08:43 AM, Markus Trippelsdorf > wrote: >> This patch breaks bootstrap: > ... > > Sorry all!! was in a rush to get in the car this morning and made a > hasty commit. Fixed for r241001 (sorry Jerry, I was a little too > slow.

Re: PING! Re: [PATCH, Fortran] Extension: COTAN and degree-valued trig intrinsics with -fdec-math

On Mon, 2016-10-11 08:43 AM, Markus Trippelsdorf wrote: > This patch breaks bootstrap: ... Sorry all!! was in a rush to get in the car this morning and made a hasty commit. Fixed for r241001 (sorry Jerry, I was a little too slow.) --- Fritz Reese

Re: [PING][PATCH 3/4][Ada,DJGPP] Ada support for DJGPP

On 10/11/2016 11:46 AM, Arnaud Charlet wrote: I'd like to ping patch https://gcc.gnu.org/ml/gcc-patches/2016-09/msg00164.html Additional comments about using ZCX_By_Default := true are in https://gcc.gnu.org/ml/gcc-patches/2016-09/msg00845.html Well this patch doesn't inspire lots of confidenc

Re: [PATCH v2] testsuite: Use -Wno-psabi instead of pruning compiler messages

On Tue, Oct 11, 2016 at 07:40:24PM +0200, Jakub Jelinek wrote: > On Tue, Oct 11, 2016 at 12:32:03PM -0500, Segher Boessenkool wrote: > > > > --- a/gcc/testsuite/g++.dg/cpp0x/constexpr-53094-3.C > > > > +++ b/gcc/testsuite/g++.dg/cpp0x/constexpr-53094-3.C > > > > @@ -1,7 +1,6 @@ > > > > // { dg-do

Re: PING! Re: [PATCH, Fortran] Extension: COTAN and degree-valued trig intrinsics with -fdec-math

On Tue, Oct 11, 2016 at 11:10:13AM -0700, Jerry DeLisle wrote: > @@ -1782,6 +1784,7 @@ radians_f (mpfr_t x, mp_rnd_t rnd_mode) > mpfr_div_d (x, x, 180.0, rnd_mode); > I forgot to point out that the above should changed to mpfr_div_ui (x, x, 180, rnd_mode); In fact, any place where

Re: PING! Re: [PATCH, Fortran] Extension: COTAN and degree-valued trig intrinsics with -fdec-math

On Tue, Oct 11, 2016 at 11:10:13AM -0700, Jerry DeLisle wrote: > > diff --git a/gcc/fortran/simplify.c b/gcc/fortran/simplify.c > index bf60f747..18135d2f 100644 > --- a/gcc/fortran/simplify.c > +++ b/gcc/fortran/simplify.c > @@ -1768,11 +1768,13 @@ degrees_f (mpfr_t x, mp_rnd_t rnd_mode) > stat

Re: PING! Re: [PATCH, Fortran] Extension: COTAN and degree-valued trig intrinsics with -fdec-math

On 10/11/2016 09:32 AM, Aaron Sawdey wrote: > On Tue, 2016-10-11 at 07:26 -0400, Fritz Reese wrote: >> On Mon, Oct 10, 2016 at 3:56 PM, Steve Kargl ... snip ... > > I think the first part of that cleanup didn't get applied as I am > seeing this: > > ../../gcc/gcc/fortran/iresolve.c: In function âg

Re: PING! Re: [PATCH, Fortran] Extension: COTAN and degree-valued trig intrinsics with -fdec-math

Hi all, attached a small patch that resolves the issues at least on x86_64-linux/F23. - Andre On Tue, 11 Oct 2016 11:32:50 -0500 Aaron Sawdey wrote: > On Tue, 2016-10-11 at 07:26 -0400, Fritz Reese wrote: > > On Mon, Oct 10, 2016 at 3:56 PM, Steve Kargl > > wrote: > > ... > > > > > > There

Re: [PATCH v2] testsuite: Use -Wno-psabi instead of pruning compiler messages

On Tue, Oct 11, 2016 at 12:32:03PM -0500, Segher Boessenkool wrote: > > > --- a/gcc/testsuite/g++.dg/cpp0x/constexpr-53094-3.C > > > +++ b/gcc/testsuite/g++.dg/cpp0x/constexpr-53094-3.C > > > @@ -1,7 +1,6 @@ > > > // { dg-do compile { target c++11 } } > > > // { dg-options "" } > > > -// Ignore w

Re: [PATCH v2] testsuite: Use -Wno-psabi instead of pruning compiler messages

On Tue, Oct 11, 2016 at 06:11:29PM +0200, Jakub Jelinek wrote: > On Tue, Oct 11, 2016 at 03:43:03PM +, Segher Boessenkool wrote: > > It is much nicer to avoid a warning than to manually prune it from the > > compiler output. This patch adds -Wno-psabi to various testcases, and > > removes dg-p

Re: [PATCH, RS6000, PR77934] mtvsrdd needs b (base register) constraint on first input

On Tue, Oct 11, 2016 at 09:39:10AM -0500, Aaron Sawdey wrote: > Gcc 7 trunk was generating incorrect code for spec2k6 403.gcc due to > this constraint issue. OK for trunk after bootstrap/regtest passes? > > 2016-10-06  Aaron Sawdey   > > PR target/77934 > * config/rs6000/vmx.md (vsx_c

Re: [PATCH], PR 77924, Fix PowerPC breakage on AIX

On Mon, Oct 10, 2016 at 04:46:53PM -0400, Michael Meissner wrote: > I accidently broke AIX with my patch on October 6th. That patch split > -mfloat128 into -mfloat128-type and -mfloat128 under PowerPC Linux. This > patch > fixes that issue. I bootstrapped it on PowerPC Linux with no regressions

Re: [PATCH] Remove x86 pcommit instruction

On Tue, Oct 11, 2016 at 10:04 AM, Andrew Senkevich wrote: > 2016-10-06 1:07 GMT+03:00 H.J. Lu : >> On Wed, Oct 5, 2016 at 1:42 PM, Andrew Senkevich >> wrote: >>> 2016-10-05 18:06 GMT+03:00 Uros Bizjak : On Wed, Oct 5, 2016 at 3:47 PM, Andrew Senkevich wrote: >> -mpcommit >> -Ta

Re: [PATCH] Remove x86 pcommit instruction

2016-10-06 1:07 GMT+03:00 H.J. Lu : > On Wed, Oct 5, 2016 at 1:42 PM, Andrew Senkevich > wrote: >> 2016-10-05 18:06 GMT+03:00 Uros Bizjak : >>> On Wed, Oct 5, 2016 at 3:47 PM, Andrew Senkevich >>> wrote: > -mpcommit > -Target Report Mask(ISA_PCOMMIT) Var(ix86_isa_flags) Save > -Suppor

Re: [PATCH,rs6000] Add built-in function support for Power9 string operations

On Mon, Oct 10, 2016 at 12:11:40PM -0600, Kelvin Nilsen wrote: > > This patch adds support for 26 new instructions that are introduced > with the Power ISA 3.0 (Power9). The instructions are lxvl, stxvl, > vcmpneb, "vcmpneb.", vcmnezb, "vcmpnezb.", vcmpneh, "vcmpneh.", vcmpnezh, > "vcmpnezh.", cm

[PATCH, alpha]: Use alpha-passes.def to register passes.

2016-10-11 Uros Bizjak * config/alpha/alpha-passes.def: New file. * config/alpha/t-alpha: New file. * config/alpha/alpha-protos.h (gcc::context, rtl_opt_pass): Declare. (make_pass_handle_trap_shadows): New prototype. (make_pass_align_insns): Ditto. * config/alpha/alpha.c

Re: PING! Re: [PATCH, Fortran] Extension: COTAN and degree-valued trig intrinsics with -fdec-math

On Tue, 2016-10-11 at 07:26 -0400, Fritz Reese wrote: > On Mon, Oct 10, 2016 at 3:56 PM, Steve Kargl > wrote: > ... > > > > There are a few small clean-up that can be > > done.  For example, > > > > +static gfc_expr * > > +get_radians (gfc_expr *deg) > > +{ > > +  mpfr_t tmp; > ... > > > > the

Re: [PATCH v2] testsuite: Use -Wno-psabi instead of pruning compiler messages

On Tue, Oct 11, 2016 at 03:43:03PM +, Segher Boessenkool wrote: > It is much nicer to avoid a warning than to manually prune it from the > compiler output. This patch adds -Wno-psabi to various testcases, and > removes dg-prune-output, for the testcases where x86 and/or PowerPC had > those (or

Re: [PATCH 09/16] Split class rtx_reader into base_rtx_reader vs rtx_reader

On 10/05/2016 06:15 PM, David Malcolm wrote: - rtx_reader_ptr->get_top_level_filename ()); + base_rtx_reader_ptr->get_top_level_filename ()); I wonder if the number of changes could be minimized by retaining the name rtx_reader for the base class, and using something more speci

[PATCH, PING*3] DWARF: space-optimize loc. descr. for integer literals on 32-bit targets

Hello, Ping for the patch submitted at . Thanks! -- Pierre-Marie de Rodat

[PATCH v2] testsuite: Use -Wno-psabi instead of pruning compiler messages

It is much nicer to avoid a warning than to manually prune it from the compiler output. This patch adds -Wno-psabi to various testcases, and removes dg-prune-output, for the testcases where x86 and/or PowerPC had those (or did warn, so the testcase failed). It also removes -w whenever there is -W

Re: PING! Re: [PATCH, Fortran] Extension: COTAN and degree-valued trig intrinsics with -fdec-math

On 10/11/2016 07:37 AM, Andrew Pinski wrote: > > Looks like it was only broken for some mpfr's. That is ones which is > compiled with gcc it worked but one which comes with Ubuntu 1604 it > does not. they are exactly the same version too. > > Thanks, > Andrew Also broken on Fedora 24. Fritz,

Re: [PATCH][check_GNU_style.sh] More aggressively ignore dg-xxx directives

On 11/10/16 16:13, Jeff Law wrote: On 10/11/2016 05:01 AM, Bernd Schmidt wrote: On 10/11/2016 12:56 PM, Jakub Jelinek wrote: On Tue, Oct 11, 2016 at 11:47:21AM +0100, Kyrill Tkachov wrote: check_GNU_style.sh complains a lot about dg-* directives in the testsuite and in particular about line l

Re: [PATCH 01/16] read-md.c: Add various cleanups to ~rtx_reader

On Wed, 2016-10-05 at 17:51 +0200, Bernd Schmidt wrote: > On 10/05/2016 06:14 PM, David Malcolm wrote: > > The selftests for the RTL frontend require supporting multiple > > reader instances being alive one after another in-process, so > > this lack of cleanup would become a leak. > > > + /* Init

Re: [PATCH][check_GNU_style.sh] More aggressively ignore dg-xxx directives

On 10/11/2016 05:01 AM, Bernd Schmidt wrote: On 10/11/2016 12:56 PM, Jakub Jelinek wrote: On Tue, Oct 11, 2016 at 11:47:21AM +0100, Kyrill Tkachov wrote: check_GNU_style.sh complains a lot about dg-* directives in the testsuite and in particular about line lengths. There's nothing we can do abo

Re: [PATCH] Split print_rtx into subroutines

On 10/11/2016 05:34 PM, David Malcolm wrote: +static void print_rtx_operand (const_rtx in_rtx, int idx); +static void print_rtx_operand_code_0 (const_rtx in_rtx, int idx); +static void print_rtx_operand_code_e (const_rtx in_rtx, int idx); +static void print_rtx_operand_codes_E_and_V (const_rtx i

[PATCH] Split print_rtx into subroutines

print_rtx is a ~550 line function, the bulk of which is a ~400-line switch statement, with a fair amount to #if logic. This patch simplifies things by moving the switch statement into its own subroutine, and by moving the more complicated cases into their own subroutines. No functional changes (b

[PATCH GCC]New vectorization pattern turning cond_expr into max/min and plus/minus

Hi, Given below test case, int foo (unsigned short a[], unsigned int x) { unsigned int i; for (i = 0; i < 1000; i++) { x = a[i]; a[i] = (unsigned short)(x >= 32768 ? x - 32768 : 0); } return x; } it now can be vectorized on AArch64, but generated assembly is way from opti

gcc-patches@gcc.gnu.org

Hi, We missed folding (convert)(X op const) -> (convert)X op (convert)const for unsigned narrowing because of reason reported at https://gcc.gnu.org/ml/gcc/2016-07/msg00126.html This patch fixes the issue by adding new match&simplify pattern, it also adds a test case. This is the prerequisite p

[PATCH, RS6000, PR77934] mtvsrdd needs b (base register) constraint on first input

Gcc 7 trunk was generating incorrect code for spec2k6 403.gcc due to this constraint issue. OK for trunk after bootstrap/regtest passes? 2016-10-06  Aaron Sawdey   PR target/77934 * config/rs6000/vmx.md (vsx_concat_): The mtvsrdd instruction needs a base register for arg 1

Re: [PATCH, PING] DWARF: process all TYPE_DECL nodes when iterating on scopes

On 09/28/2016 09:48 AM, Richard Biener wrote: Hmm, interesting approach. It might work reliably at this point of the compilation but we do actually recycle cgraph nodes. Arf, what a pity. ;-) So I wonder if given we do have ->origin / ->next_nested in the cgraph if we can simply perform a wa

Re: PING! Re: [PATCH, Fortran] Extension: COTAN and degree-valued trig intrinsics with -fdec-math

On Tue, Oct 11, 2016 at 5:43 AM, Markus Trippelsdorf wrote: > On 2016.10.11 at 07:26 -0400, Fritz Reese wrote: >> On Mon, Oct 10, 2016 at 3:56 PM, Steve Kargl >> wrote: >> ... >> > There are a few small clean-up that can be >> > done. For example, >> > >> > +static gfc_expr * >> > +get_radians (

Re: [SPARC] Tidy up Condition Code support and more

Hi Eric. +(define_insn "*plus_sltu_vis3" + [(set (match_operand:W 0 "register_operand" "=r") + (plus:W (ltu:W (match_operand 2 "icc_register_operand" "X") + (const_int 0)) + (match_operand:W 1 "arith_operand" "rI")))] + "TARGET_ARCH64 && TARG

Re: New option -flimit-function-alignment

On 10/11/2016 04:11 PM, Bernd Schmidt wrote: Denys has submitted some patches to add more capabilities to the -falign-* options, but these still have some issues, and the original ideas seems to have been to allow for large alignments without over-aligning small functions. The following patch i

New option -flimit-function-alignment

Denys has submitted some patches to add more capabilities to the -falign-* options, but these still have some issues, and the original ideas seems to have been to allow for large alignments without over-aligning small functions. The following patch implements that idea by taking into account th

Re: Compile-time improvement for if conversion.

On Tue, Oct 11, 2016 at 3:23 PM, Yuri Rumyantsev wrote: > Richard, > > I implemented this by passing callback function in_region which > returns true if block belongs to region. > I am testing it now > > I attach modified patch for your quick review. + FOR_EACH_VEC_ELT (region, i, bb) +{ +

[C++ PATCH] RFC: implement P0386R2 - C++17 inline variables

Hi! Here is an attempt to implement C++17 inline variables. Bootstrapped/regtested on x86_64-linux and i686-linux. The main question is if the inline variables, which are vague linkage, should be !DECL_EXTERNAL or DECL_EXTERNAL DECL_NOT_REALLY_EXTERN while in the FE. In the patch, they are !DECL

Re: Compile-time improvement for if conversion.

Richard, I implemented this by passing callback function in_region which returns true if block belongs to region. I am testing it now I attach modified patch for your quick review. Thanks. 2016-10-11 13:33 GMT+03:00 Richard Biener : > On Mon, Oct 10, 2016 at 4:17 PM, Yuri Rumyantsev wrote: >>

Re: [PATCH, ARM 5/7] Add support for MOVT/MOVW to ARMv8-M Baseline

On 10/10/16 13:35, Christophe Lyon wrote: Hi Thomas, Hi Christophe, On 13 July 2016 at 17:34, Thomas Preudhomme wrote: On Wednesday 13 July 2016 17:14:52 Christophe Lyon wrote: Hi Thomas, Hi Christophe, I'm seeing: gcc.target/arm/pr42574.c: syntax error in target selector "arm_thumb1

Re: [RFC][VRP] Improve intersect_ranges

On Tue, Oct 11, 2016 at 2:57 AM, kugan wrote: > Hi Richard, > > > On 10/10/16 20:13, Richard Biener wrote: >> >> On Sat, Oct 8, 2016 at 9:38 PM, kugan >> wrote: >>> >>> Hi Richard, >>> >>> Thanks for the review. >>> On 07/10/16 20:11, Richard Biener wrote: On Fri, Oct 7, 2016 at 12

Re: [libgo] Silence compiler error message

On Mon, Oct 10, 2016 at 12:44 PM, Eric Botcazou wrote: > > on Solaris the configuration of the library yields an ugly: > > checking whether linker supports split/non-split linked together... cc1: > error: '-fsplit-stack' is not supported by this compiler configuration > xgcc: error: conftest1.o: N

[PATCH] Tiny dwarf2out bits from early LTO debug

This merges a few more tiny pieces, one latent issue with -gsplit-dwarf and !DWARF2_ASM_LINE_DEBUG_INFO where we'd produce duplicate labels (happens for darwin and early LTO debug). I've merged a verify_die routine that helped me spotting invalid dwarf trees. Bootstrapped and tested on x86_64-un

[PATCH] Fix PR77931

The following fixes PR77931. Bootstrapped and tested on x86_64-unknown-linux-gnu, applied. Richard. 2016-10-11 Richard Biener PR debug/77931 * gimple-low.c (lower_gimple_bind): Handle arbitrary common sub-chains of BLOCK_VARS and gimple_bind_vars. Index: gcc/gimple-

Re: PING! Re: [PATCH, Fortran] Extension: COTAN and degree-valued trig intrinsics with -fdec-math

On 2016.10.11 at 07:26 -0400, Fritz Reese wrote: > On Mon, Oct 10, 2016 at 3:56 PM, Steve Kargl > wrote: > ... > > There are a few small clean-up that can be > > done. For example, > > > > +static gfc_expr * > > +get_radians (gfc_expr *deg) > > +{ > > + mpfr_t tmp; > ... > > the tmp variable is

Re: [PATCH, PR77558] Remove RECORD_TYPE special-casing in std_canonical_va_list_type

On 10 October 2016 at 11:53, Richard Biener wrote: > On Sun, Sep 25, 2016 at 11:08 AM, Tom de Vries wrote: >> Hi, >> >> this patch fixes PR77558, an ice-on-invalid-code 6/7 regression. >> >> The fix for PR71602 introduced the invalid-code test-case >> c-c++-common/va-arg-va-list-type.c: >> ... >>

Re: PING! Re: [PATCH, Fortran] Extension: COTAN and degree-valued trig intrinsics with -fdec-math

On Mon, Oct 10, 2016 at 3:56 PM, Steve Kargl wrote: ... > There are a few small clean-up that can be > done. For example, > > +static gfc_expr * > +get_radians (gfc_expr *deg) > +{ > + mpfr_t tmp; ... > the tmp variable is unneeded in the above. Converting the double > precision 180.0 to mpfr_t

Re: [PATCH][check_GNU_style.sh] More aggressively ignore dg-xxx directives

On 11/10/16 11:56, Jakub Jelinek wrote: On Tue, Oct 11, 2016 at 11:47:21AM +0100, Kyrill Tkachov wrote: check_GNU_style.sh complains a lot about dg-* directives in the testsuite and in particular about line lengths. There's nothing we can do about the directives and sometimes they're supposed

Re: [PATCH][check_GNU_style.sh] More aggressively ignore dg-xxx directives

On 10/11/2016 12:56 PM, Jakub Jelinek wrote: On Tue, Oct 11, 2016 at 11:47:21AM +0100, Kyrill Tkachov wrote: check_GNU_style.sh complains a lot about dg-* directives in the testsuite and in particular about line lengths. There's nothing we can do about the directives and sometimes they're suppo

Re: [PATCH][check_GNU_style.sh] More aggressively ignore dg-xxx directives

On Tue, Oct 11, 2016 at 11:47:21AM +0100, Kyrill Tkachov wrote: > check_GNU_style.sh complains a lot about dg-* directives in the testsuite and > in particular about line lengths. > There's nothing we can do about the directives and sometimes they're supposed > to be long, in particular the scan-

[PATCH][check_GNU_style.sh] More aggressively ignore dg-xxx directives

Hi all, check_GNU_style.sh complains a lot about dg-* directives in the testsuite and in particular about line lengths. There's nothing we can do about the directives and sometimes they're supposed to be long, in particular the scan-assembler checks in dg-final. Currently check_GNU_style.sh ha

[PATCH] Optimise std::list::assign(initializer_list) slightly

This is a microoptimisation to call the relevant _M_assign_dispatch function directly (because we know we have iterators), rather than calling assign() to do the dispatching. * include/bits/stl_list.h (assign(initializer_list)): Call _M_assign_dispatch directly with correct tag.

[PATCH] Simplify std::rethrow_if_nested definition

Originally this header didn't use , but we install that for freestanding builds now, so it's always available. That means we can simplify things a bit, using remove_reference, enable_if etc. This also implements the missing part of LWG 2484, so that we don't try to use dynamic_cast when the stati

[Patch, testsuite] Fix gcc.g/tree-ssa/pr59597.c failure for avr

Hi, This patch declares loop index variable j as a 32 bit int instead of assuming ints are 32 bits. The smaller int size on the avr makes prior passes optimize away the loop exit check (j < 1000), as the constant is outside the range of a 16 bit int. Committed to trunk, after reg te

Re: [PATCH][AArch64] Add spellchecking hints for -march,-mcpu,-mtune and their attributes

On Fri, Oct 07, 2016 at 01:34:37PM -0700, Andrew Pinski wrote: > On Fri, Oct 7, 2016 at 7:52 AM, Kyrill Tkachov > wrote: > > Hi all, > > > > This patch uses the spellcheck API from David and Jakub [1] to implement > > hints for the > > march, mcpu and mtune options to suggest appropriate architect

[Ada] Fix various debug info issues with renaming

GNAT encodings for object renamings that involve packed private types were not generated. This is because we were not using Underlying_Type to analyze types involved. This patch introduces Underlying_Type calls where necessary. It also generates GNAT encodings renamings for byte unaligned obj

[PATCH] Enable printers and xmethods for std::__cxx11::list

This makes the python utils work for the new ABI list (they still need to work with the new string as well). * python/libstdcxx/v6/printers.py (build_libstdcxx_dictionary): Register printer for std::__cxx11::list. * python/libstdcxx/v6/xmethods.py (ListMethodsMatcher.match

[PATCH] Remove redundant const qualifliers from string_view

These return types cause "type qualifiers ignored on function return type" warnings with -Wsystem-headers. * include/experimental/string_view (basic_string_view::_S_compare): Remove redundant const from return type. * include/std/string_view (basic_string_view:_S_compare):

MAINTAINERS

Update my email address nathan 2016-10-10 Nathan Sidwell * MAINTAINERS: Update email address. Index: MAINTAINERS === --- MAINTAINERS (revision 240920) +++ MAINTAINERS (working copy) @@ -86,7 +86,7 @@ nds32 port Shiva Chen n

[PATCH] More noexcept for standard mutex types and locks

These functions can all be noexcept (if we ever wanted to check the mutex is owned by the calling thread in the adopt_lock ctors we'd abort, not throw). * include/bits/std_mutex.h (mutex::native_handle) (lock_guard(mutex_type&, adopt_lock_t) (unique_lock(mutex_type&, adopt

  1   2   >