[Bug sanitizer/79168] [7 Regression] libtsan fails to link when cross compiling GCC tip for Aarch64 target

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79168 Jakub Jelinek changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug libstdc++/79206] New: string_view operator== could do an early exit if sizes differ

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79206 Bug ID: 79206 Summary: string_view operator== could do an early exit if sizes differ Product: gcc Version: 6.3.1 Status: UNCONFIRMED Severity: normal

[Bug c++/79205] New: ICE in create_tmp_var, at gimple-expr.c:473

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79205 Bug ID: 79205 Summary: ICE in create_tmp_var, at gimple-expr.c:473 Product: gcc Version: 7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++

Re: [libcc1] add support for C++

On Jan 23, 2017, Jason Merrill wrote: > Better to fix an inconsistent API now than leave it to confuse future > developers, I would think. Here's an incremental patch to the API, with all the proposed name changes to make the whole thing more consistent (the conventions are

[Bug go/78763] go1: internal compiler error: in do_get_backend, at go/gofrontend/expressions.cc:8352

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78763 --- Comment #12 from ian at gcc dot gnu.org --- Author: ian Date: Tue Jan 24 03:34:14 2017 New Revision: 244852 URL: https://gcc.gnu.org/viewcvs?rev=244852=gcc=rev Log: PR go/78763 Backported from mainline: compiler: call

Re: GCC 6 RFA: Go patch: call determine_types even for constant expressions

On Thu, Dec 15, 2016 at 4:25 PM, Ian Lance Taylor wrote: > On Thu, Dec 15, 2016 at 2:47 PM, Ian Lance Taylor wrote: >> The Go frontend needs to call determine_types even for constant >> expressions, which it was not doing. The problem is that a constant >>

Re: [libcc1] add support for C++

On Jan 22, 2017, Alexandre Oliva wrote: > On Jan 13, 2017, Jason Merrill wrote: >> On 09/23/2016 08:41 PM, Alexandre Oliva wrote: >>> +/* Create a modified version of a function type that has default >>> + values for some of its arguments. The returned

[Bug c/79204] New: improve -Woverflow by mentioning types and values

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79204 Bug ID: 79204 Summary: improve -Woverflow by mentioning types and values Product: gcc Version: 7.0 Status: UNCONFIRMED Severity: enhancement Priority: P3

[Bug rtl-optimization/66669] FAIL: gcc.dg/loop-8.c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=9 --- Comment #4 from kelvin at gcc dot gnu.org --- Author: kelvin Date: Tue Jan 24 01:26:13 2017 New Revision: 244850 URL: https://gcc.gnu.org/viewcvs?rev=244850=gcc=rev Log: gcc/testsuite/ChangeLog: 2017-01-23 Kelvin Nilsen

Re: [PATCH 3/5] simply handling of -Wformat-overflow/truncation options (PR 78703)

2017-01-20 Martin Sebor * gimple-ssa-sprintf.c (warn_level): New global. (format_integer): Use it here and throughout the rest of the file. Use the same switch to compute sign as base. (maybe_warn): New function. (format_directive):

[Bug middle-end/78703] -fprintf-return-value floating point handling incorrect in locales with a mulltibyte decimal point

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78703 --- Comment #8 from Martin Sebor --- Author: msebor Date: Tue Jan 24 01:10:10 2017 New Revision: 244847 URL: https://gcc.gnu.org/viewcvs?rev=244847=gcc=rev Log: PR middle-end/78703 - -fprintf-return-value floating point handling incorrect in

[Bug middle-end/78703] -fprintf-return-value floating point handling incorrect in locales with a mulltibyte decimal point

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78703 --- Comment #7 from Martin Sebor --- Author: msebor Date: Tue Jan 24 01:06:34 2017 New Revision: 244846 URL: https://gcc.gnu.org/viewcvs?rev=244846=gcc=rev Log: PR middle-end/78703 - -fprintf-return-value floating point handling incorrect in

[Bug middle-end/78703] -fprintf-return-value floating point handling incorrect in locales with a mulltibyte decimal point

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78703 --- Comment #6 from Martin Sebor --- Author: msebor Date: Tue Jan 24 00:55:19 2017 New Revision: 244845 URL: https://gcc.gnu.org/viewcvs?rev=244845=gcc=rev Log: PR middle-end/78703 - -fprintf-return-value floating point handling incorrect in

Re: [PATCH] Enable -fsanitize=thread and =leak support on ppc64{,le}

On Mon, Jan 23, 2017 at 7:20 PM, Jakub Jelinek wrote: > Hi! > > On Mon, Jan 23, 2017 at 03:32:46PM +0100, Jakub Jelinek wrote: >> I think it should be enabled if it works, even this late. >> I bet we need something like the following patch on top of >> the PR79168 patch. >> >>

Re: [libcc1] add support for C++

On Jan 23, 2017, Jason Merrill wrote: > On Sun, Jan 22, 2017 at 6:06 PM, Alexandre Oliva wrote: >> On Jan 13, 2017, Jason Merrill wrote: >> >>> On 09/23/2016 08:41 PM, Alexandre Oliva wrote: +static tree global_friend_list; >> >>>

[PATCH] Enable -fsanitize=thread and =leak support on ppc64{,le}

Hi! On Mon, Jan 23, 2017 at 03:32:46PM +0100, Jakub Jelinek wrote: > I think it should be enabled if it works, even this late. > I bet we need something like the following patch on top of > the PR79168 patch. > > I'll test both patches on both ppc64le and ppc64. > > Another question is, it

[Bug sanitizer/79168] [7 Regression] libtsan fails to link when cross compiling GCC tip for Aarch64 target

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79168 --- Comment #3 from Jakub Jelinek --- Author: jakub Date: Tue Jan 24 00:18:36 2017 New Revision: 244844 URL: https://gcc.gnu.org/viewcvs?rev=244844=gcc=rev Log: PR sanitizer/79168 * merge.sh (change_comment_headers): Don't

Re: A + B CMP A -> A CMP' CST' match.pd patterns [was [PATCH] avoid calling memset et al. with excessively large sizes (PR 79095)]

On 01/21/2017 01:00 AM, Marc Glisse wrote: On Fri, 20 Jan 2017, Jeff Law wrote: On 01/20/2017 04:30 PM, Jeff Law wrote: Going to work from the self-contained test... Here's a test case that's closer to the one from the bug. It also ends up with the out of bounds memset even at -O1,

Re: [PATCH] PR libstdc++/79195 fix make_array type deduction

On 23/01/17 18:40 -0500, David Edelsohn wrote: FAIL: experimental/array/make_array.cc (test for excess errors) Excess errors: /nasfarm/edelsohn/src/src/libstdc++v3/testsuite/experimental/array/make_array.cc:38: error: 'ref' is not a member of 'std' I wonder why I didn't see that fail,

Re: [PATCH/AARCH64] Improve ThunderX2 T99 address cost model

On 23/01/17 23:35, Andrew Pinski wrote: > Hi, > On ThunderX 2, the logical shifts that are part of the address cause > a 1 cycle extra and this is not modeled correctly. For induction > variables we don't want to do the shift. When I change the cost for > the shift of the addresses, I get a

Re: [PATCH, v2] (9e) Update "startwith" logic for pass-skipping to handle __RTL functions

On 01/19/2017 10:22 AM, David Malcolm wrote: ...the problem being that into_cfglayout's execute vfunc calls cfg_layout_initialize, which does a lot more that just cfg_layout_rtl_register_cfg_hooks (the skip hack does just the latter). + /* Don't skip df init; later RTL passes need it. */ +

Re: [PATCH] Fix libsanitizer merge (PR sanitizer/79168)

On 01/23/2017 03:28 PM, Jakub Jelinek wrote: Hi! The merge.sh script seems to remove lines 2 and 3 regardless of what they contain. If they contain the The LLVM Compiler Infrastructure comment, we do want that, but a couple of files (mostly *.S) don't contain that. The following patch ought

Re: [PATCH] PR libstdc++/79195 fix make_array type deduction

FAIL: experimental/array/make_array.cc (test for excess errors) Excess errors: /nasfarm/edelsohn/src/src/libstdc++v3/testsuite/experimental/array/make_array.cc:38: error: 'ref' is not a member of 'std'

Re: [PATCH][doc] Correct optimisation levels documentation for -fstore-merging

On 01/23/2017 10:28 AM, Kyrill Tkachov wrote: Hi all, I had forgotten to update the -fstore-merging documentation from a previous iteration of the pass and it says that it's enabled at -O and higher. The option is in fact enabled at -O2 and higher, as well as -Os. This patch clarifies that. Is

[PATCH/AARCH64] Improve ThunderX2 T99 address cost model

Hi, On ThunderX 2, the logical shifts that are part of the address cause a 1 cycle extra and this is not modeled correctly. For induction variables we don't want to do the shift. When I change the cost for the shift of the addresses, I get a 12% improvement on HMMER; all over benchmarks in

[Bug target/79203] Update PowerPC double->int conversions to know about -mvsx-small-integer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79203 Michael Meissner changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last reconfirmed|

[Bug target/79203] New: Update PowerPC double->int conversions to know about -mvsx-small-integer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79203 Bug ID: 79203 Summary: Update PowerPC double->int conversions to know about -mvsx-small-integer Product: gcc Version: 7.0 Status: UNCONFIRMED Severity:

[Bug tree-optimization/77445] [7 Regression] Performance drop after r239219 on coremark test

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77445 --- Comment #22 from Jeffrey A. Law --- In response to c#19. Yes, a thread path which is cold except for a hot block in the middle might be profitable to thread as it will sometimes expose path specific redundancies/simplifications in the hot

[Bug target/79202] On Power8, consider using vupkhsw/xxpermdi to sign extend an int in a vector register instead of mfvsrwz/mtvsrwa

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79202 Michael Meissner changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug target/79202] New: On Power8, consider using vupkhsw/xxpermdi to sign extend an int in a vector register instead of mfvsrwz/mtvsrwa

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79202 Bug ID: 79202 Summary: On Power8, consider using vupkhsw/xxpermdi to sign extend an int in a vector register instead of mfvsrwz/mtvsrwa Product: gcc Version: 7.0

[Bug libstdc++/78420] [5/6/7 Regression] std::less<T*> is not a total order with -O2 enabled

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78420 --- Comment #19 from Jonathan Wakely --- (In reply to Jens Maurer from comment #16) > That means the standard library needs to do its homework to clearly specify > under which circumstances (which argument types) it expects a constexpr >

[Bug tree-optimization/77445] [7 Regression] Performance drop after r239219 on coremark test

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77445 --- Comment #21 from Jeffrey A. Law --- In response to c#20. We have to be careful about fixing up the loop after rotation and avoid repeatedly peeling. The old threader dealt with those by being fairly conservative in passes before the loop

[Bug libstdc++/78420] [5/6/7 Regression] std::less<T*> is not a total order with -O2 enabled

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78420 --- Comment #18 from Jens Maurer --- Then you should cheat on [dcl.constexpr] p5 by carving out the nullptr case: constexpr void less_than(int *p1, int *p2) { if (p1 == nullptr && p2 == nullptr) return false; return (size_t)p1 <

Re: [patch] update zlib to the 1.2.10 release.

On 22 January 2017 at 19:42, Matthias Klose wrote: > On 22.01.2017 19:12, NightStrike wrote: >> On Sun, Jan 22, 2017 at 1:00 PM, Matthias Klose wrote: >>> NightStrike proposed to revert to the 1.2.8 release until zlib stabilizes >>> again; >>> I'm open for

[committed] neeeded -> needed

Hi! WHen looking at PR79176, I've noticed too many eees in a function name. Fixed thusly, bootstrapped/regtested on x86_64-linux and i686-linux, committed to trunk as obvious. 2017-01-23 Jakub Jelinek * tree.h (assign_assembler_name_if_neeeded): Rename to ...

[Bug libstdc++/78420] [5/6/7 Regression] std::less<T*> is not a total order with -O2 enabled

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78420 --- Comment #17 from Ville Voutilainen --- (In reply to Jens Maurer from comment #16) > I'd like to point out that there is no prohibition against writing > reinterpret_cast inside a constexpr function. It's just if you call that > function and

[Bug libstdc++/79193] libstdc++ configure incorrectly decides linking works for cross-compiler

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79193 sandra at gcc dot gnu.org changed: What|Removed |Added Status|WAITING |NEW --- Comment #2 from

[Bug libstdc++/78420] [5/6/7 Regression] std::less<T*> is not a total order with -O2 enabled

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78420 Jens Maurer changed: What|Removed |Added CC||jens.maurer at gmx dot net --- Comment

[Bug tree-optimization/79088] [7 Regression] wrong code at -O2 on x86_64-linux-gnu

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79088 Jeffrey A. Law changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug tree-optimization/79188] [7 Regression] wrong code at -O3 on x86_64-linux-gnu

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79188 Jeffrey A. Law changed: What|Removed |Added Status|NEW |RESOLVED CC|

[Bug tree-optimization/79188] [7 Regression] wrong code at -O3 on x86_64-linux-gnu

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79188 --- Comment #3 from Jeffrey A. Law --- Author: law Date: Mon Jan 23 22:29:17 2017 New Revision: 244837 URL: https://gcc.gnu.org/viewcvs?rev=244837=gcc=rev Log: 2017-01-23 Richard Biener PR tree-optimization/79088

[Bug tree-optimization/79088] [7 Regression] wrong code at -O2 on x86_64-linux-gnu

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79088 --- Comment #6 from Jeffrey A. Law --- Author: law Date: Mon Jan 23 22:29:17 2017 New Revision: 244837 URL: https://gcc.gnu.org/viewcvs?rev=244837=gcc=rev Log: 2017-01-23 Richard Biener PR tree-optimization/79088

[PATCH] Fix libsanitizer merge (PR sanitizer/79168)

Hi! The merge.sh script seems to remove lines 2 and 3 regardless of what they contain. If they contain the The LLVM Compiler Infrastructure comment, we do want that, but a couple of files (mostly *.S) don't contain that. The following patch ought to fix that. Bootstrapped/regtested on

[Bug testsuite/79071] Add test case for PR/65618

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79071 Maciej W. Rozycki changed: What|Removed |Added CC|

Re: [PR middle-end/79123] cast false positive in -Walloca-larger-than=

On 01/19/2017 05:17 AM, Aldy Hernandez wrote: In the attached testcase, we have a clearly bounded case of alloca which is being incorrectly reported: void g (int *p, int *q) { size_t n = (size_t)(p - q); if (n < 10) f (__builtin_alloca (n)); } The problem is that VRP gives us an

Re: [PR middle-end/79123] cast false positive in -Walloca-larger-than=

On 01/19/2017 05:17 AM, Aldy Hernandez wrote: In the attached testcase, we have a clearly bounded case of alloca which is being incorrectly reported: void g (int *p, int *q) { size_t n = (size_t)(p - q); if (n < 10) f (__builtin_alloca (n)); } The problem is that VRP gives us an

libgo patch committed: Update to go1.8rc2

I have committed a patch to libgo to update to the go1.8rc2 release candidate. This uncovered a bug in the calculation of the hash code for reflect.FuncOf, which is fixed by this patch. I noticed while doing the merge that somewhere along the way a bunch of testdata files were dropped. I added

Re: [PATCH] Fix false positive for -Walloc-size-larger-than (PR, bootstrap/79132).

On 01/19/2017 04:46 AM, Martin Liška wrote: Hello. Following patch fixes asan bootstrap, as mentioned in the PR. Ready to be installed? Thanks, Martin 0001-Fix-false-positive-for-Walloc-size-larger-than-PR-bo.patch From 6a3d1b85e124751fdb804ae86596d30ea98b54af Mon Sep 17 00:00:00 2001

[Bug libstdc++/78420] [5/6/7 Regression] std::less<T*> is not a total order with -O2 enabled

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78420 --- Comment #15 from Jason Merrill --- (In reply to Ville Voutilainen from comment #14) > Not in general, no, it doesn't have to always give a compile-time answer. > But I believe the library intent is that when it compares compile-time >

[Bug target/77300] [MIPS] incorrectly moves instruction containing local GOT16 relocation into a delay slot

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77300 --- Comment #6 from Maciej W. Rozycki --- Fixed in binutils now: commit 65060a78866f374e25f4668d12efc783235d19d1 Author: Maciej W. Rozycki Date: Wed Jan 18 18:18:21 2017 + PR gas/20649: MIPS:

Re: [PR 79108] Put ipa_node_params to GC memory

Hi Martin, > when I fixed PR 78365 by streaming types of parameters that might not > have been anywhere else, I forgot that I was holding them in non-GC > memory and so I caused PR 79108. The following patch fixes it by > putting ipa_param_descriptor and ipa_node_params structures into GC >

Re: [PR c++/78469] default ctor makes dtor required

On Wed, Jan 18, 2017 at 1:25 PM, Nathan Sidwell wrote: > I've figured out what's happening here. Just not sure of the most prudent > way to fix it. > > struct no_destr { > no_destr() = default; > > protected: > ~no_destr() = default; > }; > > void *Foo () > { > return new

[Bug libstdc++/78420] [5/6/7 Regression] std::less<T*> is not a total order with -O2 enabled

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78420 --- Comment #14 from Ville Voutilainen --- Not in general, no, it doesn't have to always give a compile-time answer. But I believe the library intent is that when it compares compile-time constant pointers, it should give that answer at

[Bug libstdc++/78420] [5/6/7 Regression] std::less<T*> is not a total order with -O2 enabled

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78420 --- Comment #13 from Jason Merrill --- (In reply to Ville Voutilainen from comment #11) > Ah, the plot thickens. Jens Maurer wrote: > > "Regarding the std::less issue, it seems a bug in the standard > to require that it be constexpr and

[Bug bootstrap/79198] [7 Regression] r244802 causes out of memory during PGO bootstrap

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79198 --- Comment #7 from Martin Jambor --- And based on the IRC discussion I had earlier today with Markus, I have also added the following to the patch I'm bootstrapping, even though it is not strictly necessary to prevent OOM in the testcase from

Re: [C++ PATCH] 79118 bitfields & constexpr

On Mon, Jan 23, 2017 at 4:13 PM, Jakub Jelinek wrote: > On Mon, Jan 23, 2017 at 04:06:22PM -0500, Jason Merrill wrote: >> > The right solution is to fix the IR. In the C++ FE have BITFIELD_REF (or a >> > new node) look much more like COMPONENT_REF (or even be COMPONENT_REF, but

[Bug middle-end/56727] Recursive call goes through the PLT unnecessarily

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56727 --- Comment #8 from Alexander Monakov --- Well, if my argument is correct, then GCC generates wrong code for the very first example in comment #0. If that is deliberate as a compromise even though otherwise GCC suppresses optimizations to honor

[Bug target/78936] Interprocedural constant propagation miscompiles C++ methods on i686 Windows

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78936 --- Comment #3 from Reid Kleckner --- The compiled code still fails at runtime during an LLVM build in the same way.

Re: A + B CMP A -> A CMP' CST' match.pd patterns [was [PATCH] avoid calling memset et al. with excessively large sizes (PR 79095)]

On 01/23/2017 02:10 AM, Richard Biener wrote: I think it was added for the reason stated in the comment: /* When one argument is a constant, overflow detection can be simplified. Currently restricted to single use so as not to interfere too much with ADD_OVERFLOW detection in

Re: [C++ PATCH] 79118 bitfields & constexpr

On Mon, Jan 23, 2017 at 04:06:22PM -0500, Jason Merrill wrote: > > The right solution is to fix the IR. In the C++ FE have BITFIELD_REF (or a > > new node) look much more like COMPONENT_REF (or even be COMPONENT_REF, but I > > suspect lots of places think ADDR (COMPONENT_REF (...)) is legit).

Re: [C++ PATCH] 79118 bitfields & constexpr

On Mon, Jan 23, 2017 at 8:49 AM, Nathan Sidwell wrote: > This patch addresses 79118, where we ICE on a constexpr involving bitfields > in an unnamed struct (unnamed struct members are a g++ extension). > > This is really a band-aid, because our internal representation BITFIELD_REF

[Bug sanitizer/79200] Race-Condition in Address Santitizer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79200 Martin Liška changed: What|Removed |Added CC||marxin at gcc dot gnu.org --- Comment #1

[Bug c++/79192] Angle bracket following typename is treated as template argument delimiter even if the name is not a template name

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79192 Jonathan Wakely changed: What|Removed |Added Keywords||rejects-valid

[Bug bootstrap/79198] [7 Regression] r244802 causes out of memory during PGO bootstrap

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79198 --- Comment #6 from Martin Jambor --- I am about to test the following, which fixes the test from comment #1. It does fix a clear bug in the patch I committed today, without it there we multitudes of identical cgraph duplication hooks active at

Re: [PATCH] Fix PR79088/79188

On 01/23/2017 06:17 AM, Richard Biener wrote: The following is a fix for jump-threading loop-assumption clearing which was done only on the first header/irreducible crossing rather than the one at the destination of the threading path. Bootstrapped and tested on x86_64-unknown-linux-gnu, ok

[Bug fortran/79165] 100% compile-time increase for polyhedron aermod by r244581

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79165 David Malcolm changed: What|Removed |Added Status|ASSIGNED|NEW Assignee|dmalcolm at gcc

[Bug fortran/79165] 100% compile-time increase for polyhedron aermod by r244581

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79165 --- Comment #12 from David Malcolm --- Looking at the line maps, we have a sane list of ordinary linemaps, but then the linemap_add call at line 4761 here: 4758tree 4759build_translation_unit_decl (tree name) 4760{ 4761

Re: [PATCH 5/5] add support for width and precision ranges (PR 78703)

On 01/22/2017 04:53 PM, Martin Sebor wrote: This is the last patch in the series. It adds logic to handle non-constant width and precision with range information to help reduce both false positives false negatives. The patch replaces the scalar width and precision with two element arrays

[PATCH] -fsanitize=address,undefined support on s390x

On Mon, Jan 23, 2017 at 04:10:01PM +0100, Ulrich Weigand wrote: > Bill Schmidt wrote: > > On Jan 23, 2017, at 8:32 AM, Jakub Jelinek wrote: > > > > > > Another question is, it seems upstream has s390{,x}-*-linux* support for > > > asan/ubsan, does that work? In that case we

[Bug c++/79192] Angle bracket following typename is treated as template argument delimiter even if the name is not a template name

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79192 --- Comment #1 from ricilake at gmail dot com --- Thanks to Johannes Schaub-litb (via SO), the problem appears to be at around line 16781 of cp/parser.c: /* There is no valid C++ program where a non-template type is followed by a

[Bug c++/71710] [7 Regression] ICE on valid C++11 code with decltype and alias template: in lookup_member, at cp/search.c:1255

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71710 --- Comment #4 from Nathan Sidwell --- Author: nathan Date: Mon Jan 23 20:24:32 2017 New Revision: 244833 URL: https://gcc.gnu.org/viewcvs?rev=244833=gcc=rev Log: PR c++/71710 - template using directive of field * pt.c

Re: [C++ Patch/RFC] PR 72764

On Mon, Jan 23, 2017 at 11:15 AM, Paolo Carlini wrote: > in this relatively serious ICE on invalid regression (we don't emit any > message before ICEing) make_typename_type, called by strip_typedefs, returns > error_mark_node which then isn't handled by

[Bug c++/71710] [7 Regression] ICE on valid C++11 code with decltype and alias template: in lookup_member, at cp/search.c:1255

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71710 Nathan Sidwell changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug fortran/79165] 100% compile-time increase for polyhedron aermod by r244581

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79165 David Malcolm changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|unassigned

[Bug c++/71406] [7 Regression] ICE on valid C++ code on x86_64-linux-gnu: in finish_class_member_access_expr, at cp/typeck.c:2782

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71406 Nathan Sidwell changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug c++/77508] [7 Regression] ICE on valid C++ code: in finish_class_member_access_expr, at cp/typeck.c:2783

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77508 Nathan Sidwell changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug c++/77508] [7 Regression] ICE on valid C++ code: in finish_class_member_access_expr, at cp/typeck.c:2783

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77508 --- Comment #4 from Nathan Sidwell --- Author: nathan Date: Mon Jan 23 20:19:07 2017 New Revision: 244832 URL: https://gcc.gnu.org/viewcvs?rev=244832=gcc=rev Log: PR c++/71406 - ICE with scope-ref'd template id exprs PR

[Bug c++/71406] [7 Regression] ICE on valid C++ code on x86_64-linux-gnu: in finish_class_member_access_expr, at cp/typeck.c:2782

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71406 --- Comment #3 from Nathan Sidwell --- Author: nathan Date: Mon Jan 23 20:19:07 2017 New Revision: 244832 URL: https://gcc.gnu.org/viewcvs?rev=244832=gcc=rev Log: PR c++/71406 - ICE with scope-ref'd template id exprs PR

Re: [c== pATCH] 71710 dependent FIELD_DECL

On Mon, Jan 23, 2017 at 12:09 PM, Nathan Sidwell wrote: > Jason, > Bug 71710 is a crash on 'decltype (a)', where 'a' is a FIELD_DECL wth > dependent type. finish_class_member_access_expr barfs on that. The earlier > sequence of if..elses has a check for FIELD_DECL, but that's in

Re: [C++ PATCH] 71406, 77508 scoped template_ids

OK. On Mon, Jan 23, 2017 at 1:53 PM, Nathan Sidwell wrote: > This patch fixes 71406 and 77508, which are both ICEs dealing with > 'X::Foo<...>'. finish_class_member_access_expr wasn't prepared to handle > SCOPE_REF (TEMPLATE_ID_EXPR (...)), which is what it was being fed. Fixed

Re: [libcc1] add support for C++

On Sun, Jan 22, 2017 at 6:06 PM, Alexandre Oliva wrote: > On Jan 13, 2017, Jason Merrill wrote: > >> On 09/23/2016 08:41 PM, Alexandre Oliva wrote: >>> +static tree global_friend_list; > >> This should be a hash_set rather than a TREE_LIST. > > You sure? At

Re: [PATCH 3/5] simply handling of -Wformat-overflow/truncation options (PR 78703)

On 01/22/2017 04:53 PM, Martin Sebor wrote: The attached patch is the last of the refactoring/restructuring series. It consists of the following changes: 1) Introduce a single global variable, warn_level, that the pass uses to test the level of the warning that applies to the function

[Bug bootstrap/79198] [7 Regression] r244802 causes out of memory during PGO bootstrap

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79198 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment #5

Re: [PATCH 2/5] remove unused member (PR 78703)

On 01/22/2017 04:52 PM, Martin Sebor wrote: The attached simple patch removes the format_result::constant member that is not used except in debugging dumps. Removing it makes the handling of non-constant arguments simpler. Since this handling increases in the substantive changes that follow

Re: [patch, fortran] Warn about integer**(negative integer)

Hi FX, The idea seems reasonable, but I am not sure about the wording (“truncated” in particular). “Integer exponentiation truncated to constant 0”? Why not “Negative integer exponent has result value zero”? Other than that, OK to commit. You're right, the error message was a bit strange.

Re: [PATCH] Fix PR78189

Hi Nick, On 23 January 2017 at 10:04, Richard Biener wrote: > On Fri, 20 Jan 2017, Nick Clifton wrote: > >> Hi Guys, >> >> [I have been asked to look at this PR in the hopes that it can be >> fixed soon and so no longer act as a blocker for the gcc 7 branch]. >> >> It

[Bug c/79082] -Wformat-truncation inconsistent behaviour

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79082 --- Comment #8 from Martin Sebor --- > case 3. You can see that in the dump created by the -ftree-dump-vrp option > where the argument is assumed to include the negative subrange: > > Value ranges after VRP: > ... > iftmp.0_11: [-99, 99]

New Danish PO file for 'cpplib' (version 7.1-b20170101)

Hello, gentle maintainer. This is a message from the Translation Project robot. A revised PO file for textual domain 'cpplib' has been submitted by the Danish team of translators. The file is available at: http://translationproject.org/latest/cpplib/da.po (This file,

Contents of PO file 'cpplib-7.1-b20170101.da.po'

cpplib-7.1-b20170101.da.po.gz Description: Binary data The Translation Project robot, in the name of your translation coordinator.

[Bug c/79082] -Wformat-truncation inconsistent behaviour

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79082 --- Comment #7 from Martin Sebor --- Except for #8, none of the sprintf calls in the extended testcase in attachment 40566 can be handled as accurately at -O0 as with optimization because the arguments to the format directives are treated as if

Re: [RFC] fix bootstrap on aarch64-*-freebsd and probably others

On 23/01/17 18:00, Andreas Tobler wrote: > On 23.01.17 18:48, Jakub Jelinek wrote: >> On Mon, Jan 23, 2017 at 06:42:15PM +0100, Andreas Tobler wrote: >>> Something like below? >>> >>> If ok, I can commit, right? >>> >>> Thanks, >>> >>> Andreas >>> >>> 2017-01-23 Andreas Tobler

[Bug middle-end/56727] Recursive call goes through the PLT unnecessarily

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56727 --- Comment #7 from Yuri Gribov --- (In reply to Alexander Monakov from comment #6) > Note that even without symbol aliases, such calls are not necessarily > self-recursive when 'f' is first called via dlsym with RTLD_NEXT or a > specific module

[C++ PATCH] 71406, 77508 scoped template_ids

This patch fixes 71406 and 77508, which are both ICEs dealing with 'X::Foo<...>'. finish_class_member_access_expr wasn't prepared to handle SCOPE_REF (TEMPLATE_ID_EXPR (...)), which is what it was being fed. Fixed by moving the SCOPE_REF splitting to before the TEMPLATE_ID_EXPR handling, but

[Bug target/70012] test case gcc.dg/vect/costmodel/ppc/costmodel-vect-33.c fails

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70012 Bill Schmidt changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |wschmidt at gcc dot gnu.org ---

Re: [PATCH 1/5] consolidate handling of directives (PR 78703)

On 01/22/2017 04:52 PM, Martin Sebor wrote: The substance of the attached change set is to lay the groundwork of consolidating the handling of format directives and conversion specifications. 1) Extend (and rename) struct conversion_spec used thus far to represent a format conversion

[Bug target/78936] Interprocedural constant propagation miscompiles C++ methods on i686 Windows

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78936 --- Comment #2 from Reid Kleckner --- That option does not appear to affect the linked portions of the assembly. The " [clone .constprop.544]" transform still appears to fire. I will run the complete build and get back soon.

Re: [PATCH][doc] Correct optimisation levels documentation for -fstore-merging

On 01/23/2017 10:28 AM, Kyrill Tkachov wrote: Hi all, I had forgotten to update the -fstore-merging documentation from a previous iteration of the pass and it says that it's enabled at -O and higher. The option is in fact enabled at -O2 and higher, as well as -Os. This patch clarifies that. Is

[Bug middle-end/79176] [6/7 Regression] ICE in mangle_decl with LTO and Os

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79176 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment #2

[Bug target/70012] test case gcc.dg/vect/costmodel/ppc/costmodel-vect-33.c fails

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70012 --- Comment #3 from Bill Schmidt --- It looks to me like vect_alignment_reachable is the wrong test to be using here. This is equivalent to vect_aligned_arrays || natural_alignment_32. vect_aligned_array is always 0 for powerpc*-*-*.

[Bug target/79197] [5/6/7 Regression] ICE in extract_insn in gcc/recog.c:2311

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79197 --- Comment #4 from Jakub Jelinek --- Yeah, or -mcpu=power8 -mno-popcntd -mvsx -mvsx-scalar-double even if gas has power7/power8 support.

  1   2   3   4   >