Re: [PATCH] libbacktrace: Fix compile warning building testcase

On Fri, Mar 3, 2017 at 6:46 AM, Sam Thursfield wrote: > > I hit this compile warning running `make check` on AIX. Since -Werror is > enabled by default here it causes a build failure. > > Tested on powerpc-ibm-aix7.2.0.0 > > This my first patch submission for GCC,

Re: [PATCH] fix error spelling in nds32.c (PR 79928)

Martin Sebor on 2017/3/8 08:09 wrote: The following one-line patch corrects the spelling of the error message in the nds32 back end pointed out by a translator. I'll go ahead and commit it as trivial unless there are objections in the next day or so. Martin 2017-03-07 Martin Sebor

[PATCH] add calls.c to GTFILES in Makefile.in

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. (Thanks again to David Malcolm who helped

[PATCH] fix error spelling in nds32.c (PR 79928)

The following one-line patch corrects the spelling of the error message in the nds32 back end pointed out by a translator. I'll go ahead and commit it as trivial unless there are objections in the next day or so. Martin 2017-03-07 Martin Sebor *

stabilize store merging

Don't let pointer randomization change the order in which we process store chains. This may cause SSA_NAMEs to be released in different order, and if they're reused later, they may cause differences in SSA partitioning, leading to differences in expand, and ultimately to different code.

Re: [PATCH] [PATCH, rs6000] Fix pr79941

On Tue, 2017-03-07 at 22:52 +0100, Jakub Jelinek wrote: > On Tue, Mar 07, 2017 at 03:36:38PM -0600, Will Schmidt wrote: > > Per PR79941, we are folding the vec_mul{e,o}* operations improperly. Those > > entries were added to the intrinsics-to-be-folded list where the generic > > multiplies should

Re: [PATCH] For broken exception handling in GDB on AIX platform

On 7 March 2017 13:43:00 CET, Nitish Kumar Mishra wrote: >Hi, > >I have update the patch according to some comments from GDB community. >Please find the attachments. If it is AIX specific, you probably should not remove fuchsia support. And since we most likely do

Re: [PATCH] [PATCH, rs6000] Fix pr79941

On Tue, Mar 07, 2017 at 03:36:38PM -0600, Will Schmidt wrote: > Per PR79941, we are folding the vec_mul{e,o}* operations improperly. Those > entries were added to the intrinsics-to-be-folded list where the generic > multiplies should have been instead. Test coverage in place was for the > generic

[PATCH] [PATCH, rs6000] Fix pr79941

Hi, Per PR79941, we are folding the vec_mul{e,o}* operations improperly. Those entries were added to the intrinsics-to-be-folded list where the generic multiplies should have been instead. Test coverage in place was for the generic multiplies, and this was missed by my testing. Thusly, remove

Updating config.guess (was: i386-unknown-freebsd -> i586-unknown-freebsd)

On Tue, 7 Mar 2017, Jeff Law wrote: >> When/if this has been accepted, is it okay to pull the latest config.guess >> into GCC even at this stage of the release process? (We're only looking >> at this change and the addition of nsx-tandem compared to what we have >> right now.) > If it's just

[PATCH] Don't ICE if the Fortran FE calls some stor-layout.c etc. function that emits warning, -Wpadded fixes (PR fortran/79886)

Hi! The Fortran FE registers its own format decoder, overriding the default one that handles what the middle-end can emit, e.g. warning (OPT_Wpadded, "padding struct to align %q+D", field); The C/C++ FEs are the only other ones that override the decoder, but they do handle all the specs the

[committed] OpenMP/OpenACC invalid pragma location diagnostics (PR c/79834)

Hi! This patch should make life easier for the translators by emitting just one translatable message about pragmas only allowed in compound statements, instead of 13 different ones. In addition to that it stops using c*_parser_error for that, both so that the msgid can use %s and to avoid

[C++ PATCH] Fix error-recovery in maybe_thunk_body (PR c++/79899)

Hi! Apparently in error recovery, populate_clone_array can't return fns with all NULLs. maybe_thunk_body used to handle that fine, but the newly added ctor_omit_inherited_parms call ICEs. Fixed thusly, bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk? 2017-03-07 Jakub

[C++ PATCH] Fix error-recovery for invalid enumerators (PR c++/79896)

Hi! Doing copy_node on error_mark_node doesn't work too well, lots of spots in the compiler assume there is just a single error_mark_node and compare it using pointer comparison, rather than checking for TREE_CODE () == ERROR_MARK. The testcase ICEs in particular during gimplification, the

[PATCH] Small ubsan vector arith optimization to fix one testcase from PR sanitizer/79904

Hi! If any of the operands of the UBSAN_{ADD,SUB,MUL}_OVERFLOW ifn with vector operand is a uniform vector, expanding it as VCE on the VECTOR_CST followed by ARRAY_REF with variable index in the loop is unnecessarily expensive and nothing fixes it afterwards. This works around ICE on s390 at

[PATCH] Fix up avx512vlintrin.h with -O0 (PR target/79932)

Hi! I've preprocessed x86intrin.h with -O0 and -O2, both with -E -dD, and gathered all _mm starting inline function names at column zero and #define _mm macro names and compared them. This revealed that 64 intrinsics have similar bug in avx512vlintrin.h, no other problems found.

[PATCH] Fix up avx512bwintrin.h with -O0 (PR target/79932)

Hi! As mentioned in the PR, 6 intrinsics were only defined in section guarded with #ifdef __OPTIMIZE__ (unnecessarily, because the intrinsics don't have any immediate argument that must be constant) and without #defines for -O0. Fixed thusly, bootstrapped/regtested on x86_64-linux and

Re: [PATCH] Fix PR79345, better uninit warnings for memory

On 03/01/2017 07:03 AM, Richard Biener wrote: The following addresses a regression in uninit warnings that happens because clobber stmts preclude the very simple-minded support we have for memory. The patch fixes this by instead implementing uninit warnings for memory properly, using the alias

C++ PATCH to fix ICE in replace_placeholders_r (PR c++/79937)

In this testcase we have C c = bar (X{1}); which store_init_value sees as c = TARGET_EXPR i}>)> i.e. we're initializing "c" with a TARGET_EXPR. We call replace_placeholders that walks the whole tree to substitute the placeholders. Eventually we

Re: C PATCH to fix ICE with old-style parameter declarations with initializers (PR sanitizer/79757)

On 03/06/2017 02:44 PM, Marek Polacek wrote: This is an ICE with -fsanitize=undefined on invalid code involving old-style parameter declarations and nested functions. Ugh. Old-style parameter declarations cannot have initializers, and start_decl errors when it sees that something's trying to

Re: i386-unknown-freebsd -> i586-unknown-freebsd

On 03/04/2017 09:40 AM, Gerald Pfeifer wrote: On Tue, 24 May 2016, Richard Biener wrote: As Jeff noted, i386 actually is the "marketing" name used for the platform, GCC has been defaulting to i486 for ages, and I upgraded to i586 last year: 2015-11-15 Gerald Pfeifer

Re: [PATCH] Fix ICE with -Walloca-larger-than=[>INT_MAX] (PR middle-end/79809)

On 03/02/2017 05:32 AM, Marek Polacek wrote: As demonstrated by this test, we can crash on the assert in alloca_call_type: gcc_assert (is_vla || warn_alloca_limit > 0); when -Walloca-larger-than= receives an argument greater than INT_MAX. Even though warn_vla_limit is marked as UInteger in

Re: [PATCH] Increment value instead of a pointer in ADA macro processing.

On 03/07/2017 03:30 AM, Martin Liška wrote: Hello. Looks there's real issues spotted by -Wchkp: ../../gcc/c-family/c-ada-spec.c: In function ‘void print_ada_macros.chkp(pretty_printer*, \xe2\x80\x98pointer_bounds_typ\xe2\x80\x99 not supported by dump_type#, cpp_hashnode**,

Re: i386-unknown-freebsd -> i586-unknown-freebsd

On 03/04/2017 09:44 AM, Gerald Pfeifer wrote: On Tue, 24 May 2016, Richard Biener wrote: Can we update to a non-marketing name then, like i586-unknown-freebsd please? config.gcc accepts i[34567]86-*-freebsd*. It at least confused me. Of course, once I hacked config.gcc, I realized that the

Re: [PATCH 4/5] Disable -fcheck-pointer-bounds with sanitizers.

On Mon, Mar 06, 2017 at 02:07:37PM +0100, marxin wrote: > PR target/65705 > PR target/69804 > * toplev.c (process_options): Disable -fcheck-pointer-bounds with > sanitizers. I can understand why it is disabled for -fsanitize=address or -fsanitize=bounds, perhaps

Re: [PATCH] PR ada/66205 gnatbind generates invalid code when finalization is enabled in restricted runtime

On 19 Dec 2015, at 22:05, Simon Wright wrote: > > On 12 Nov 2015, at 10:02, Arnaud Charlet wrote: >> This situation arises, for example, with an embedded RTS that incorporates the Ada 2012 generalized container iterators. >>> >>> I

Re: [PATCH 2/5] Get bounds for a PARM_DECL (PR ipa/79761).

On 03/07/2017 09:07 AM, Martin Liška wrote: On 03/07/2017 03:57 PM, Richard Biener wrote: On Thu, Mar 2, 2017 at 6:06 PM, marxin wrote: gcc/ChangeLog: 2017-03-06 Martin Liska PR ipa/79761 * tree-chkp.c (chkp_get_bound_for_parm): Get bounds

Re: [PATCH 4/5] Disable -fcheck-pointer-bounds with sanitizers.

On 03/06/2017 06:07 AM, marxin wrote: gcc/ChangeLog: 2017-03-06 Martin Liska PR target/65705 PR target/69804 * toplev.c (process_options): Disable -fcheck-pointer-bounds with sanitizers. gcc/testsuite/ChangeLog: 2017-03-06 Martin Liska

Re: [PATCH 1/5] Fix *_CST ICEs connected to MPX.

On 03/07/2017 03:53 PM, Richard Biener wrote: > On Tue, Mar 7, 2017 at 3:48 PM, Martin Liška wrote: >> On 03/07/2017 11:17 AM, Rainer Orth wrote: >>> marxin writes: >>> diff --git a/gcc/testsuite/g++.dg/pr79769.C b/gcc/testsuite/g++.dg/pr79769.C

Re: [PATCH 2/5] Get bounds for a PARM_DECL (PR ipa/79761).

On 03/07/2017 03:57 PM, Richard Biener wrote: > On Thu, Mar 2, 2017 at 6:06 PM, marxin wrote: >> gcc/ChangeLog: >> >> 2017-03-06 Martin Liska >> >> PR ipa/79761 >> * tree-chkp.c (chkp_get_bound_for_parm): Get bounds for a param. >>

Re: [PATCH 5/5] Support BIT_FIELD_REF in MPX (PR ipa/79764).

On Tue, Mar 7, 2017 at 3:49 PM, Martin Liška wrote: > On 03/07/2017 11:18 AM, Rainer Orth wrote: >> marxin writes: >> >>> diff --git a/gcc/testsuite/g++.dg/pr79764.C b/gcc/testsuite/g++.dg/pr79764.C >>> new file mode 100644 >>> index 000..47fb88da19b >>>

Re: [PATCH 2/5] Get bounds for a PARM_DECL (PR ipa/79761).

On Thu, Mar 2, 2017 at 6:06 PM, marxin wrote: > gcc/ChangeLog: > > 2017-03-06 Martin Liska > > PR ipa/79761 > * tree-chkp.c (chkp_get_bound_for_parm): Get bounds for a param. > (chkp_find_bounds_1): Remove gcc_unreachable. > >

Re: [PATCH 1/5] Fix *_CST ICEs connected to MPX.

On Tue, Mar 7, 2017 at 3:48 PM, Martin Liška wrote: > On 03/07/2017 11:17 AM, Rainer Orth wrote: >> marxin writes: >> >>> diff --git a/gcc/testsuite/g++.dg/pr79769.C b/gcc/testsuite/g++.dg/pr79769.C >>> new file mode 100644 >>> index 000..f9223db1b2d >>>

Re: [PATCH 5/5] Support BIT_FIELD_REF in MPX (PR ipa/79764).

On 03/07/2017 11:18 AM, Rainer Orth wrote: > marxin writes: > >> diff --git a/gcc/testsuite/g++.dg/pr79764.C b/gcc/testsuite/g++.dg/pr79764.C >> new file mode 100644 >> index 000..47fb88da19b >> --- /dev/null >> +++ b/gcc/testsuite/g++.dg/pr79764.C >> @@ -0,0 +1,12 @@ >>

Re: [PATCH 1/5] Fix *_CST ICEs connected to MPX.

On 03/07/2017 11:17 AM, Rainer Orth wrote: > marxin writes: > >> diff --git a/gcc/testsuite/g++.dg/pr79769.C b/gcc/testsuite/g++.dg/pr79769.C >> new file mode 100644 >> index 000..f9223db1b2d >> --- /dev/null >> +++ b/gcc/testsuite/g++.dg/pr79769.C >> @@ -0,0 +1,4 @@ >>

Re: [PATCH 2/5] Get bounds for a PARM_DECL (PR ipa/79761).

On 03/07/2017 11:16 AM, Rainer Orth wrote: > marxin writes: > >> diff --git a/gcc/testsuite/g++.dg/pr79761.C b/gcc/testsuite/g++.dg/pr79761.C >> new file mode 100644 >> index 000..b1f92d2b036 >> --- /dev/null >> +++ b/gcc/testsuite/g++.dg/pr79761.C >> @@ -0,0 +1,34 @@ >>

Re: [PATCH 0/5] Fix various MPX issues

On 03/07/2017 11:26 AM, Uros Bizjak wrote: > Hello! > >> I'm sending a small series that fixes MPX issue that are quite easily >> fixable. >> The series can bootstrap on ppc64le and survives regression tests. > > Several testcases in the serie are put outside gcc.target/i386 > directory. You

[OBVIOUS][PATCH] gcov: put comment to correct location.

Hello. The issues was created when I added new option (-x). Martin >From 4015b8f22dbdf8d3019ce4a8927c5f91bef7258b Mon Sep 17 00:00:00 2001 From: marxin Date: Tue, 7 Mar 2017 14:51:08 +0100 Subject: [PATCH] gcov: put comment to correct location. gcc/ChangeLog: 2017-03-07

Re: [PATCH, rs6000][GCC6] Fix PR78543, ICE in push_reload on powerpc64le-linux-gnu

Peter Bergner wrote: > If we look at rs6000_mode_dependent_address(), it accepts some addresses > as not being mode dependent: > > case PLUS: > /* Any offset from virtual_stack_vars_rtx and arg_pointer_rtx > is considered a legitimate address before reload, so there >

Re: [PATCH] For broken exception handling in GDB on AIX platform

Hi, I have update the patch according to some comments from GDB community. Please find the attachments. Thanks and Regards, Nitish K Mishra On Wed, Mar 1, 2017 at 1:33 PM, Nitish Kumar Mishra wrote: > Hi, > I have opened a defect for the same here: >

Re: [PATCH] PR libstdc++/79789 fix non-reserved names in headers

On 03/03/17 10:47 -0500, David Edelsohn wrote: This patch caused a new regression on AIX. - David FAIL: 17_intro/names.cc (test for excess errors) Excess errors: /tmp/GCC/gcc/include-fixed/sys/types.h:600: error: expected unqualified-id before '[' token

Re: [PATCH] i386: Do not align small stack slots to 16 bytes

On Tue, Mar 07, 2017 at 08:23:17AM +0100, Uros Bizjak wrote: > > 2017-03-06 Segher Boessenkool > > > > * gcc/config/i386/i386.c (ix86_local_alignment): Align most > > aggregates > > of 16 bytes and more to 16 bytes, not those of 16 bits and more. >

[PATCH] Fix MIPS-specific ICE in gcc.dg/pr77834.c (PR rtl-optimization/79150).

Hi, This ICE is caused by "gcc_assert (!JUMP_P (last))" in commit_one_edge_insertion (gcc/cfgrtl.c): if (returnjump_p (last)) { /* ??? Remove all outgoing edges from BB and add one for EXIT. This is not currently a problem because this only happens for the (single)

[PATCH] Increment value instead of a pointer in ADA macro processing.

Hello. Looks there's real issues spotted by -Wchkp: ../../gcc/c-family/c-ada-spec.c: In function ‘void print_ada_macros.chkp(pretty_printer*, \xe2\x80\x98pointer_bounds_typ\xe2\x80\x99 not supported by dump_type#, cpp_hashnode**, \xe2\x80\x98pointer_bounds_typ\xe2\x80\x99 not supported by

Re: [PATCH 0/5] Fix various MPX issues

Hello! > I'm sending a small series that fixes MPX issue that are quite easily fixable. > The series can bootstrap on ppc64le and survives regression tests. Several testcases in the serie are put outside gcc.target/i386 directory. You need full target specifier in these cases, "{ { i?86-*-*

Re: [PATCH 1/5] Fix *_CST ICEs connected to MPX.

Hello! > 2017-03-06 Martin Liska > > PR target/79763 > PR target/79769 > PR target/79770 > * tree-chkp.c (chkp_find_bounds_1): Handle REAL_CST, > COMPLEX_CST and VECTOR_CST. > > gcc/testsuite/ChangeLog: > > 2017-03-06 Martin Liska > > PR target/79763 > PR

Re: [PATCH 5/5] Support BIT_FIELD_REF in MPX (PR ipa/79764).

marxin writes: > diff --git a/gcc/testsuite/g++.dg/pr79764.C b/gcc/testsuite/g++.dg/pr79764.C > new file mode 100644 > index 000..47fb88da19b > --- /dev/null > +++ b/gcc/testsuite/g++.dg/pr79764.C > @@ -0,0 +1,12 @@ > +/* { dg-do compile { target { ! x32 } } } */ > +/* {

Re: [PATCH 1/5] Fix *_CST ICEs connected to MPX.

marxin writes: > diff --git a/gcc/testsuite/g++.dg/pr79769.C b/gcc/testsuite/g++.dg/pr79769.C > new file mode 100644 > index 000..f9223db1b2d > --- /dev/null > +++ b/gcc/testsuite/g++.dg/pr79769.C > @@ -0,0 +1,4 @@ > +/* { dg-do compile { target { ! x32 } } } */ > +/* {

Re: [PATCH 2/5] Get bounds for a PARM_DECL (PR ipa/79761).

marxin writes: > diff --git a/gcc/testsuite/g++.dg/pr79761.C b/gcc/testsuite/g++.dg/pr79761.C > new file mode 100644 > index 000..b1f92d2b036 > --- /dev/null > +++ b/gcc/testsuite/g++.dg/pr79761.C > @@ -0,0 +1,34 @@ > +/* { dg-do compile { target { ! x32 } } } */ > +/* {

[PATCH 3/5] Fix ICE in tree-chkp-opt.c (PR tree-optimization/79631).

gcc/ChangeLog: 2017-03-06 Martin Liska PR tree-optimization/79631 * tree-chkp-opt.c (chkp_is_constant_addr): Call tree_int_cst_sign_bit just for INTEGER constants. gcc/testsuite/ChangeLog: 2017-03-06 Martin Liska PR

[PATCH 4/5] Disable -fcheck-pointer-bounds with sanitizers.

gcc/ChangeLog: 2017-03-06 Martin Liska PR target/65705 PR target/69804 * toplev.c (process_options): Disable -fcheck-pointer-bounds with sanitizers. gcc/testsuite/ChangeLog: 2017-03-06 Martin Liska PR target/65705

[PATCH 2/5] Get bounds for a PARM_DECL (PR ipa/79761).

gcc/ChangeLog: 2017-03-06 Martin Liska PR ipa/79761 * tree-chkp.c (chkp_get_bound_for_parm): Get bounds for a param. (chkp_find_bounds_1): Remove gcc_unreachable. gcc/testsuite/ChangeLog: 2017-03-06 Martin Liska PR

[PATCH 5/5] Support BIT_FIELD_REF in MPX (PR ipa/79764).

gcc/ChangeLog: 2017-03-06 Martin Liska PR ipa/79764 * tree-chkp.c (chkp_narrow_bounds_for_field): Fix typo in comment. (chkp_narrow_size_and_offset): New function. (chkp_parse_array_and_component_ref): Support BIT_FIELD_REF.

[PATCH 1/5] Fix *_CST ICEs connected to MPX.

gcc/ChangeLog: 2017-03-06 Martin Liska PR target/79763 PR target/79769 PR target/79770 * tree-chkp.c (chkp_find_bounds_1): Handle REAL_CST, COMPLEX_CST and VECTOR_CST. gcc/testsuite/ChangeLog: 2017-03-06 Martin Liska

[PATCH 0/5] Fix various MPX issues

Hello. I'm sending a small series that fixes MPX issue that are quite easily fixable. The series can bootstrap on ppc64le and survives regression tests. Thanks for review, Martin marxin (5): Fix *_CST ICEs connected to MPX. Get bounds for a PARM_DECL (PR ipa/79761). Fix ICE in

Fix IRA issue, PR79728

Hello! > 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 are > inflated because we

Re: [PATCH] Fix PR79887

On Tue, 7 Mar 2017, Christophe Lyon wrote: > Hi Richard, > > > On 6 March 2017 at 13:05, Richard Biener wrote: > > > > This fixes a crash when we try to re-use a folded loop_vectorized_call > > when vectorizing an epilogue. > > > > Bootstrapped on x86_64-unknown-linux-gnu,

[PATCH] PR c/79855: add full stop to store merging param descriptions

Committing as obvious. Thanks, Kyrill 2017-03-07 Kyrylo Tkachov PR c/79855 * params.def (PARAM_STORE_MERGING_ALLOW_UNALIGNED): Add full stop to end of description. (PARAM_MAX_STORES_TO_MERGE): Likewise. diff --git a/gcc/params.def b/gcc/params.def

Re: [PATCH] Fix GC PCH bug in dwarf2out.c (PR c++/79821)

On Tue, Mar 07, 2017 at 09:55:19AM +0100, Richard Biener wrote: > > --- gcc/dwarf2out.h.jj 2017-01-01 12:45:37.0 +0100 > > +++ gcc/dwarf2out.h 2017-03-06 12:13:48.809589411 +0100 > > @@ -163,7 +163,7 @@ enum dw_val_class > > /* Describe a floating point constant value, or a vector

Re: [PATCH] Fix GC PCH bug in dwarf2out.c (PR c++/79821)

On Mon, Mar 6, 2017 at 9:56 PM, Jakub Jelinek wrote: > Hi! > > gengtype.c considers all GC arrays with char/unsigned char/signed char > element type as strings, for which it computes size e.g. in gt_pch_note_object > using: > if (note_ptr_fn == gt_pch_p_S) > (*slot)->size

Re: [PATCH] Use array_at_struct_end_p in tree-chkp.c (PR middle-end/68270).

On Mon, Mar 6, 2017 at 2:20 PM, Martin Liška wrote: > Hello. > > As mentioned by Richard ([1]), the function should be used instead of > DECL_CHAIN(..) checking. > > Patch can bootstrap on ppc64le-redhat-linux and survives regression tests. > > Ready to be installed? Ok. Richard.

Re: [PATCH] Fix PR79887

Hi Richard, On 6 March 2017 at 13:05, Richard Biener wrote: > > This fixes a crash when we try to re-use a folded loop_vectorized_call > when vectorizing an epilogue. > > Bootstrapped on x86_64-unknown-linux-gnu, testing in progress. > > Richard. > > 2017-03-06 Richard

Re: [PATCH] Fix ubsan ICE (PR sanitizer/79897)

On Mon, 6 Mar 2017, Jeff Law wrote: > On 03/06/2017 03:58 PM, Jakub Jelinek wrote: > > Hi! > > > > Apparently fold_build_addr_expr doesn't make the argument addressable, > > it is only made addressable during following gimplification and that is too > > late here. > Yea. There's some special