[Bug fortran/92018] ICE in gfc_conv_constant_to_tree, at fortran/trans-const.c:370

2019-10-11 Thread kargl at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92018 kargl at gcc dot gnu.org changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--

[Bug fortran/92072] [10 Regression] ICE on include from other directory

2019-10-11 Thread anlauf at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92072 --- Comment #2 from anlauf at gcc dot gnu.org --- The ICE also disappears if an empty line is added between the PUBLIC statement and the INCLUDE.

[Bug fortran/92072] [10 Regression] ICE on include from other directory

2019-10-11 Thread anlauf at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92072 --- Comment #3 from anlauf at gcc dot gnu.org --- The ICE also disappears if the include file starts with an empty line.

[Bug c++/92049] bogus errors with -fchecking=2

2019-10-11 Thread mpolacek at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92049 --- Comment #6 from Marek Polacek --- Author: mpolacek Date: Fri Oct 11 20:44:02 2019 New Revision: 276906 URL: https://gcc.gnu.org/viewcvs?rev=276906&root=gcc&view=rev Log: PR c++/92049 - extra error with -fchecking=2. The concepts merge broug

[Bug c++/92049] [10 Regression] bogus errors with -fchecking=2

2019-10-11 Thread mpolacek at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92049 Marek Polacek changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|unassigned a

[Bug c++/92049] [10 Regression] bogus errors with -fchecking=2

2019-10-11 Thread mpolacek at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92049 Marek Polacek changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug c++/92070] [10 regression] -fchecking=2 error: taking address of rvalue

2019-10-11 Thread mpolacek at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92070 --- Comment #4 from Marek Polacek --- Author: mpolacek Date: Fri Oct 11 20:53:26 2019 New Revision: 276907 URL: https://gcc.gnu.org/viewcvs?rev=276907&root=gcc&view=rev Log: PR c++/92070 - bogus error with -fchecking=2. * g++.dg/expr/co

[Bug c++/92070] [10 regression] -fchecking=2 error: taking address of rvalue

2019-10-11 Thread mpolacek at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92070 Marek Polacek changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug c++/91930] [10 Regression] internal compiler error: in lazily_declare_fn, at cp/method.c:2423 with -fconcepts

2019-10-11 Thread dcb314 at hotmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91930 David Binderman changed: What|Removed |Added CC||dcb314 at hotmail dot com --- Comment

[Bug tree-optimization/92069] [10 Regression] ice in vect_analyze_scalar_cycles_1, at tree-vect-loop.c:560

2019-10-11 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92069 Andrew Pinski changed: What|Removed |Added Keywords||ice-on-valid-code Target|

[Bug c++/90998] [9/10 Regression] ICE (segfalut) in gcc/cp/call.c compare_ics() with -std=c++17

2019-10-11 Thread dan at stahlke dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90998 Dan Stahlke changed: What|Removed |Added CC||dan at stahlke dot org --- Comment #3 from

[Bug c++/92073] New: references/pointers to thread_local are not constant expressions

2019-10-11 Thread tyker at outlook dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92073 Bug ID: 92073 Summary: references/pointers to thread_local are not constant expressions Product: gcc Version: 10.0 Status: UNCONFIRMED Severity: normal

[Bug fortran/90297] gcc/fortran/resolve.c: 2 * possibly redundant code ?

2019-10-11 Thread kargl at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90297 --- Comment #6 from kargl at gcc dot gnu.org --- (In reply to David Binderman from comment #1) > svn blame says: > > 182796 pault for (args= e->value.function.actual; args; args = > args->next) > 182796 pault { > 18279

[Bug ipa/92074] New: [10 regression] 26% performance regression on Spec2017 548.exchange2_r

2019-10-11 Thread linkw at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92074 Bug ID: 92074 Summary: [10 regression] 26% performance regression on Spec2017 548.exchange2_r Product: gcc Version: 10.0 Status: UNCONFIRMED Severity: normal

[Bug middle-end/26241] [7/8/9 Regression] None of the IPA passes are documented in passes.texi

2019-10-11 Thread egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26241 Eric Gallager changed: What|Removed |Added Summary|[7/8/9/10 Regression] None |[7/8/9 Regression] None of

[Bug middle-end/81512] duplicate note in -Walloca-larger-than and alloca in a return statement

2019-10-11 Thread egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81512 Eric Gallager changed: What|Removed |Added CC||dmalcolm at gcc dot gnu.org,

[Bug c++/90052] Warning for (x == 1 && x == 2) [i.e. -Wlogical-op] should be in -Wall

2019-10-11 Thread egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90052 Eric Gallager changed: What|Removed |Added Summary|Warning for (x == 1 && x == |Warning for (x == 1 && x ==

[Bug target/91796] Sub-optimal YMM register allocation.

2019-10-11 Thread glisse at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91796 --- Comment #7 from Marc Glisse --- (In reply to Maxim Egorushkin from comment #3) > It seems to me that register allocation has been a weak spot in gcc for > years. Most such testcases show issues with arguments/return in very small functions,

[Bug tree-optimization/91775] Can eliminate compare from loop with known number of iterations

2019-10-11 Thread linkw at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91775 --- Comment #7 from Kewen Lin --- (In reply to Richard Biener from comment #5) > > probably also a missed-optimization for the new doloop stuff? Thanks for the information! This looks a good case with zero doloop_cost_for_address, but the dolo

<    1   2