[Bug c/79969] C FE emits locus of forward enum declaration rather than definition into debug info

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79969 --- Comment #2 from Jakub Jelinek --- https://gcc.gnu.org/ml/gcc-patches/2009-09/msg01161.html was the corresponding change for structs.

[Bug c/79969] C FE emits locus of forward enum declaration rather than definition into debug info

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79969 Jakub Jelinek changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last reconfirmed|

[Bug c/79969] New: C FE emits locus of forward enum declaration rather than definition into debug info

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79969 Bug ID: 79969 Summary: C FE emits locus of forward enum declaration rather than definition into debug info Product: gcc Version: 7.0 Status: UNCONFIRMED

[Bug fortran/79968] New: diagnostics: merge similar diagnostics containing -fdec-structure

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79968 Bug ID: 79968 Summary: diagnostics: merge similar diagnostics containing -fdec-structure Product: gcc Version: 7.0 Status: UNCONFIRMED Severity: normal

[Bug c++/79865] ICE calling member function with template parameter from generic lambda

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79865 Martin Sebor changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug c++/79961] Should diagnose when '__nonnull__' attribute is applied to implicit this argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79961 --- Comment #12 from Pedro Alves --- TBC, the reason I filed this, is because GDB had an incorrect use like that that survived for a few months: https://sourceware.org/ml/gdb-patches/2016-11/msg00933.html until someone compiled GDB with

[Bug c++/79961] Should diagnose when '__nonnull__' attribute is applied to implicit this argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79961 --- Comment #11 from Pedro Alves --- > All the interesting calls here are undefined. I meant that the one pointed out is undefined even without the nonnull attribute. I.e., it's not a use case that justifies supporting nonnull(1) on

[Bug driver/79882] Lack of bounds checking on -ftemplate-depth argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79882 Martin Sebor changed: What|Removed |Added Keywords||rejects-valid

[Bug c++/79961] Should diagnose when '__nonnull__' attribute is applied to implicit this argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79961 --- Comment #10 from Martin Sebor --- All the interesting calls here are undefined. The point of the example is to highlight that the nonnull attribute on the typedef typedef void F (void*) __attribute__ ((__nonnull__ (1))); is interpreted

[Bug c++/79797] [5/6 Regression] ICE with NSDMI, this pointer and constexpr

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79797 Jason Merrill changed: What|Removed |Added Summary|[5/6/7 Regression] ICE with |[5/6 Regression] ICE with

[Bug c++/79797] [5/6/7 Regression] ICE with NSDMI, this pointer and constexpr

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79797 --- Comment #3 from Jason Merrill --- Author: jason Date: Thu Mar 9 01:01:18 2017 New Revision: 245986 URL: https://gcc.gnu.org/viewcvs?rev=245986=gcc=rev Log: PR c++/79797 - ICE with self-reference in array DMI. * constexpr.c

[Bug c++/79961] Should diagnose when '__nonnull__' attribute is applied to implicit this argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79961 --- Comment #9 from Pedro Alves --- > ((A*)0)->g (p) This is undefined behavior. We forced the world to fix code like that in the GCC 6 release cycle: https://gcc.gnu.org/gcc-6/changes.html At best, I'd suggest degrading the error on

[Bug c++/79967] New: ICE on non-type template argument declared noreturn

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79967 Bug ID: 79967 Summary: ICE on non-type template argument declared noreturn Product: gcc Version: 7.0 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug c++/79961] Should diagnose when '__nonnull__' attribute is applied to implicit this argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79961 Martin Sebor changed: What|Removed |Added CC||msebor at gcc dot gnu.org --- Comment #8

[Bug bootstrap/79952] [7 Regression] ICE in test_loading_cfg in read-rtl-function.c:2016 targeting hppa2.0w-hp-hpux11.11

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79952 David Malcolm changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last reconfirmed|

[Bug target/79928] nds32: misspelled diagnostic: not support -fpic

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79928 Martin Sebor changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug target/79928] nds32: misspelled diagnostic: not support -fpic

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79928 Martin Sebor changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug c++/79961] Should diagnose when '__nonnull__' attribute is applied to implicit this argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79961 --- Comment #7 from Pedro Alves --- Funny enough, clang 3.7 (don't have more recent handy), warns in that case, while it errors on the "this" arg: nonnull.cc:3:39: error: '__nonnull__' attribute is invalid for the implicit this argument A

[Bug c++/79961] Should diagnose when '__nonnull__' attribute is applied to implicit this argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79961 --- Comment #6 from Pedro Alves --- I remembered to check what does G++ say when you apply the nonnull to a non-pointer argument. We get a hard error: $ /opt/gcc/bin/g++ nonnull.cc -o nonnull -c nonnull.cc:5:67: error: nonnull argument

[Bug rtl-optimization/79949] ICE in Max. number of generated reload insns per insn is achieved (90)

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

[Bug ipa/79966] New: [6/7 Regression] run time more than twice slower when using -fipa-cp-clone

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79966 Bug ID: 79966 Summary: [6/7 Regression] run time more than twice slower when using -fipa-cp-clone Product: gcc Version: 7.0.1 Status: UNCONFIRMED Severity:

[Bug c++/79950] G++ cannot detect simple off by one error in STL classes

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79950 Martin Sebor changed: What|Removed |Added CC||msebor at gcc dot gnu.org --- Comment #7

[Bug bootstrap/79952] [7 Regression] ICE in test_loading_cfg in read-rtl-function.c:2016 targeting hppa2.0w-hp-hpux11.11

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79952 Jeffrey A. Law changed: What|Removed |Added CC||law at redhat dot com --- Comment #2

[Bug rtl-optimization/79916] ICE in Max. number of generated reload insns per insn is achieved (90)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79916 --- Comment #6 from Vladimir Makarov --- I still can not reproduce it but I hope the fix for PR 79949 will be also a fix for this PR.

[Bug rtl-optimization/79949] ICE in Max. number of generated reload insns per insn is achieved (90)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79949 --- Comment #3 from Vladimir Makarov --- The fix will be ready tomorrow.

[Bug rtl-optimization/79949] ICE in Max. number of generated reload insns per insn is achieved (90)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79949 --- Comment #2 from Vladimir Makarov --- I've reproduced it and started to work on it.

[Bug target/79965] [7 Regression] OpenMP simd, invalid instructions on ia32 core2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79965 --- Comment #6 from Jakub Jelinek --- Yes, they chose to only do SSE2 and nothing else by default (and need to use special clauses otherwise). We chose to do SSE2, AVX, AVX2, AVX512F. Of course only for exported functions, for TU local ones it

[Bug target/79965] [7 Regression] OpenMP simd, invalid instructions on ia32 core2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79965 --- Comment #5 from Harald Anlauf --- (In reply to Jakub Jelinek from comment #4) > Yeah, and that is needed for ABI reasons. > In this case it doesn't seem to be missing AVX2 support, but missing AVX512F > support. > Anyway, just upgrade your

[Bug target/79965] [7 Regression] OpenMP simd, invalid instructions on ia32 core2

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

[Bug target/79965] [7 Regression] OpenMP simd, invalid instructions on ia32 core2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79965 --- Comment #3 from Andrew Pinski --- (In reply to Harald Anlauf from comment #2) > (In reply to Andrew Pinski from comment #1) > > Your binutils does not support AVX-2 ... > > No, it does not. As I wrote, it's a dated machine. > > But for

[Bug target/79965] [7 Regression] OpenMP simd, invalid instructions on ia32 core2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79965 --- Comment #2 from Harald Anlauf --- (In reply to Andrew Pinski from comment #1) > Your binutils does not support AVX-2 ... No, it does not. As I wrote, it's a dated machine. But for -march=core2 there should be no AVX instructions anyway.

[Bug target/79965] [7 Regression] OpenMP simd, invalid instructions on ia32 core2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79965 --- Comment #1 from Andrew Pinski --- Your binutils does not support AVX-2 ...

[Bug fortran/79965] New: [7 Regression] OpenMP simd, invalid instructions on ia32 core2

-S -fverbose-asm Hi, the following code leads to invalid instructions on a dated machine (arch=core2): % cat gfcbug139.f90 pure real function add(a,b) !$omp declare simd(add) real ,intent(in) :: a,b add=a+b end function add % gfc-trunk --version | head -1 GNU Fortran (GCC) 7.0.1 20170

[Bug c++/79797] [5/6/7 Regression] ICE with NSDMI, this pointer and constexpr

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79797 Jason Merrill changed: What|Removed |Added Status|NEW |ASSIGNED CC|

[Bug libfortran/79956] [7 Regression] many new -Wmaybe-uninitialized warnings with bootstrap-O3

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79956 --- Comment #10 from Markus Trippelsdorf --- Most of the warnings are gone due to the patch. These are the remaining ones: libgfortran/generated/reshape_c16.c:266:12: warning: ‘sstride[0]’ may be used uninitialized in this function

[Bug target/79395] Compile error with -mcpu=power9 and __builtin_vec_vcmpne_p

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79395 kelvin at gcc dot gnu.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug libfortran/79956] [7 Regression] many new -Wmaybe-uninitialized warnings with bootstrap-O3

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79956 --- Comment #9 from Thomas Koenig --- Created attachment 40925 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40925=edit Patch to fix the libfortran issue Based on Comment#6, this is a patch for the libfortran issue. I am currently

[Bug target/79964] New: Cortex A53 codegen still not optimal

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79964 Bug ID: 79964 Summary: Cortex A53 codegen still not optimal Product: gcc Version: 7.0.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target

[Bug c++/79961] Should diagnose when '__nonnull__' attribute is applied to implicit this argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79961 --- Comment #5 from Pedro Alves --- > We certainly should allow __attribute__((nonnull)) on methods, even when that > > includes nonnull (implicit) also for this. Yes, agreed, with implicit nonnull with no specified argument. For the case of

[Bug c++/79960] [5/6/7 Regression] Class template partial specializations for const volatile types don't match

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79960 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org,

[Bug c++/79961] Should diagnose when '__nonnull__' attribute is applied to implicit this argument

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

[Bug c/79940] [6 Regression] OpenMP pragma - internal compiler error with taskloop

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79940 Jakub Jelinek changed: What|Removed |Added Summary|[6/7 Regression] OpenMP |[6 Regression] OpenMP

[Bug target/79909] ICE error: invalid rtl sharing found in the insn on ppc64le

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79909 Pat Haugen changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug target/79963] New: vec_eq_any extracts wrong CR bit when compiling with -mcpu=power9

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79963 Bug ID: 79963 Summary: vec_eq_any extracts wrong CR bit when compiling with -mcpu=power9 Product: gcc Version: 7.0 Status: UNCONFIRMED Severity: normal

[Bug rtl-optimization/79806] [5/6/7 Regression] ICE error: unable to find a register to spill (in assign_by_spills, at lra-assigns.c:1457)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79806 Bernd Schmidt changed: What|Removed |Added CC||bernds at gcc dot gnu.org --- Comment

[Bug translation/79618] prevent missing space in multiline string literals

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79618 David Malcolm changed: What|Removed |Added CC||dmalcolm at gcc dot gnu.org --- Comment

[Bug c++/79900] [5/6/7 Regression] ICE in strip_typedefs, at cp/tree.c:1554

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79900 Jason Merrill changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|unassigned

[Bug c/79940] [6/7 Regression] OpenMP pragma - internal compiler error with taskloop

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79940 --- Comment #6 from Jakub Jelinek --- Author: jakub Date: Wed Mar 8 17:21:06 2017 New Revision: 245980 URL: https://gcc.gnu.org/viewcvs?rev=245980=gcc=rev Log: PR c/79940 * gimplify.c (gimplify_omp_for): Replace index var in

[Bug libfortran/79956] [7 Regression] many new -Wmaybe-uninitialized warnings with bootstrap-O3

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79956 --- Comment #8 from rguenther at suse dot de --- On March 8, 2017 4:43:05 PM GMT+01:00, "marxin at gcc dot gnu.org" wrote: >https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79956 > >--- Comment #7 from Martin Liška --- >I

[Bug fortran/79886] [5/6/7 Regression] ICE in pp_format, at pretty-print.c:681

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79886 --- Comment #5 from Manuel López-Ibáñez --- The first one seems the right approach. It will also fix a number of similar bugs in one go.The second one seems more fragile and it doesn't help in decoupling ME from FE more than the first.

[Bug target/79905] ICE in canonical types differ for identical types __vector(4) int and V4i {aka __vector(4) int}

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79905 Pat Haugen changed: What|Removed |Added CC||pthaugen at gcc dot gnu.org --- Comment #2

[Bug c++/79962] New: [7 Regression] ICE nonnull_check_p on a function template with a type-dependent attribute nonnull

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79962 Bug ID: 79962 Summary: [7 Regression] ICE nonnull_check_p on a function template with a type-dependent attribute nonnull Product: gcc Version: 7.0 Status: UNCONFIRMED

[Bug c++/79961] Should diagnose when '__nonnull__' attribute is applied to implicit this argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79961 Jonathan Wakely changed: What|Removed |Added Keywords||diagnostic

[Bug c++/79961] Should diagnose when '__nonnull__' attribute is applied to implicit this argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79961 --- Comment #2 from Pedro Alves --- Yeah, I think it's too late, and it'd cause trouble with compatibility with clang. Note that the documentation for the attribute(format)

[Bug gcov-profile/79891] Wrong count of line coverage in case of gcov -a

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

[Bug c++/79961] Should diagnose when '__nonnull__' attribute is applied to implicit this argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79961 --- Comment #1 from Jonathan Wakely --- IMHO it would be much, much better if the implicit 'this' wasn't counted and nonnull(1) referred to 'arg' but maybe it's too late to change that.

[Bug c++/79950] G++ cannot detect simple off by one error in STL classes

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79950 --- Comment #6 from Jonathan Wakely --- (In reply to Jonathan Wakely from comment #5) > (In reply to David Binderman from comment #4) > > Anyway, I think some progress could be made by finding the pattern > > > > for (something = 0;

[Bug c++/79950] G++ cannot detect simple off by one error in STL classes

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79950 --- Comment #5 from Jonathan Wakely --- (In reply to David Binderman from comment #4) > (In reply to Jonathan Wakely from comment #3) > > And for this example it's possible that g(int) modifies the vector that the > > reference v is bound to >

[Bug libfortran/79956] [7 Regression] many new -Wmaybe-uninitialized warnings with bootstrap-O3

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79956 --- Comment #7 from Martin Liška --- I can also see profiledbootstrap failure in: .././../gcc/simplify-rtx.c:6021:12: error: ‘result_s’ may be used uninitialized in this function [-Werror=maybe-uninitialized] return result_s;

[Bug c++/79961] New: Should diagnose when '__nonnull__' attribute is applied to implicit this argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79961 Bug ID: 79961 Summary: Should diagnose when '__nonnull__' attribute is applied to implicit this argument Product: gcc Version: unknown Status: UNCONFIRMED

[Bug libstdc++/78939] [C++17] interferes with structured binding from struct

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78939 --- Comment #11 from Jonathan Wakely --- Oops, that was the previous diff, I meant to paste this (which constrains the __enable_if_has_tuple_size to only be used when _Tp has no cv-quals, so we avoid ambiguities): ---

[Bug libstdc++/78939] [C++17] interferes with structured binding from struct

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78939 --- Comment #10 from Jonathan Wakely --- This works around the ambiguity that PR 79960 describes: --- a/libstdc++-v3/include/std/utility +++ b/libstdc++-v3/include/std/utility @@ -88,24 +88,23 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION struct

[Bug demangler/70909] Libiberty Demangler segfaults (4)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70909 --- Comment #48 from Pedro Alves --- GDB is released separately from binutils though, and GDB 8.0 is going to branch very soon. IWBN to have this in the binutils-gdb repo by then.

[Bug c++/79950] G++ cannot detect simple off by one error in STL classes

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79950 --- Comment #4 from David Binderman --- (In reply to Jonathan Wakely from comment #3) > And for this example it's possible that g(int) modifies the vector that the > reference v is bound to I doubt g can modify v. Anyway, I think some progress

[Bug c++/79960] [5/6/7 Regression] Class template partial specializations for const volatile types don't match

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79960 --- Comment #1 from Jonathan Wakely --- It's possible this isn't a bug, and the partial specializations need to be constrained to avoid the ambiguity (although both Clang trunk and EDG accept the unconstrained cases, but Clang 3.x fails

[Bug target/70549] insn does not satisfy its constraints aarch64 gcc-4.8

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70549 --- Comment #8 from Jakub Jelinek --- Created attachment 40924 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40924=edit gcc48-pr70549.patch Bernd came up with this untested fix. Isn't that something that should be done on the trunk too?

[Bug demangler/70909] Libiberty Demangler segfaults (4)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70909 --- Comment #47 from Markus Trippelsdorf --- (In reply to Avi Kivity from comment #46) > Hopefully, the fix can be propagated to gdb's demangler soon. Unfortunately binutils 2.28 was released a few days ago. The next release will be in August

[Bug demangler/70909] Libiberty Demangler segfaults (4)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70909 --- Comment #46 from Avi Kivity --- Hopefully, the fix can be propagated to gdb's demangler soon.

[Bug c++/79960] [5/6/7 Regression] Class template partial specializations for const volatile types don't match

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79960 Richard Biener changed: What|Removed |Added Target Milestone|--- |5.5

[Bug libstdc++/78939] [C++17] interferes with structured binding from struct

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78939 --- Comment #9 from Jonathan Wakely --- (In reply to Jonathan Wakely from comment #8) > These all fail for the same reason, and I think it's a FE bug. Reported as PR 79960 (seems to be a regression since 4.9)

[Bug c++/79960] New: [5/6/7 Regression] Class template partial specializations for const volatile types don't match

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79960 Bug ID: 79960 Summary: [5/6/7 Regression] Class template partial specializations for const volatile types don't match Product: gcc Version: 7.0.1 Status: UNCONFIRMED

[Bug c/79959] New: -Wimplicit-fallthrough doesn't recognize some more complex exit cases

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79959 Bug ID: 79959 Summary: -Wimplicit-fallthrough doesn't recognize some more complex exit cases Product: gcc Version: 7.0.1 Status: UNCONFIRMED Severity: normal

[Bug libstdc++/78939] [C++17] interferes with structured binding from struct

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78939 --- Comment #8 from Jonathan Wakely --- No, no change. I think we need to change the tuple_size specializations to be incomplete when tuple_size is incomplete, even though that appears to contradict the changes made by lwg 2770. ---

[Bug c++/79957] [C++] Zero-length array function parameters in templates should cause warning/substituion failure in pedantic mode

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

[Bug c++/79950] G++ cannot detect simple off by one error in STL classes

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79950 --- Comment #3 from Jonathan Wakely --- And for this example it's possible that g(int) modifies the vector that the reference v is bound to, so the size could even change on every loop iteration. So if we added some runtime checks to std::vector

[Bug c++/79950] G++ cannot detect simple off by one error in STL classes

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79950 --- Comment #2 from Jonathan Wakely --- The C++ front-end could be taught about std::vector::size() as a special case, but that would only help that special case, it wouldn't help for std::deque::size(), or boost::vector::size() or other types.

[Bug demangler/67264] Infinite recursion of demangler on fuzzed input

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67264 Bug 67264 depends on bug 70909, which changed state. Bug 70909 Summary: Libiberty Demangler segfaults (4) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70909 What|Removed |Added

[Bug demangler/67264] Infinite recursion of demangler on fuzzed input

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67264 Markus Trippelsdorf changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC|

[Bug demangler/70909] Libiberty Demangler segfaults (4)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70909 Markus Trippelsdorf changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug demangler/70909] Libiberty Demangler segfaults (4)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70909 --- Comment #44 from Markus Trippelsdorf --- Author: trippels Date: Wed Mar 8 14:28:38 2017 New Revision: 245978 URL: https://gcc.gnu.org/viewcvs?rev=245978=gcc=rev Log: Fix PR demangler/70909 and 67264 (endless demangler recursion)

[Bug demangler/67264] Infinite recursion of demangler on fuzzed input

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67264 --- Comment #4 from Markus Trippelsdorf --- Author: trippels Date: Wed Mar 8 14:28:38 2017 New Revision: 245978 URL: https://gcc.gnu.org/viewcvs?rev=245978=gcc=rev Log: Fix PR demangler/70909 and 67264 (endless demangler recursion) ChangeLog:

[Bug c++/79950] G++ cannot detect simple off by one error in STL classes

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79950 --- Comment #1 from Jonathan Wakely --- The two cases are not equivalent, because the bounds of a[10] are known at compile-time, but v.size() is not. The only way to know v.size() is with a run-time check, which has a non-zero cost.

[Bug tree-optimization/79347] [7 regression] vect_do_peeling is messing up profile

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79347 --- Comment #15 from ro at CeBiTec dot Uni-Bielefeld.DE --- > --- Comment #14 from amker at gcc dot gnu.org --- > Fixed. The failure on sparc-sun-solaris2.12 should be resolved by patch to > PR77536. It is indeed. Thanks. Rainer

[Bug c++/79727] -Wimplicit-fallthrough=3 doesn't seem to match any comments

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79727 Peter Eisentraut changed: What|Removed |Added CC||peter at eisentraut dot org ---

[Bug tree-optimization/79958] New: Missed tree DSE

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79958 Bug ID: 79958 Summary: Missed tree DSE Product: gcc Version: 7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization

[Bug tree-optimization/79955] GLIBC build fails after r245840

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79955 Richard Biener changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug tree-optimization/79955] GLIBC build fails after r245840

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79955 --- Comment #3 from Richard Biener --- Author: rguenth Date: Wed Mar 8 14:10:47 2017 New Revision: 245976 URL: https://gcc.gnu.org/viewcvs?rev=245976=gcc=rev Log: 2017-03-08 Richard Biener PR

[Bug tree-optimization/79943] Loop splitting breaks with loops of pointer type

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79943 Andrew Haley changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug libfortran/79956] [7 Regression] many new -Wmaybe-uninitialized warnings with bootstrap-O3

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79956 --- Comment #6 from Richard Biener --- Index: libgfortran/generated/parity_l8.c === --- libgfortran/generated/parity_l8.c (revision 245968) +++ libgfortran/generated/parity_l8.c

[Bug libfortran/79956] [7 Regression] many new -Wmaybe-uninitialized warnings with bootstrap-O3

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79956 --- Comment #5 from rguenther at suse dot de --- On Wed, 8 Mar 2017, trippels at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79956 > > --- Comment #3 from Markus Trippelsdorf --- > Testcase that only warns with -O3

[Bug libfortran/79956] [7 Regression] many new -Wmaybe-uninitialized warnings with bootstrap-O3

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79956 Richard Biener changed: What|Removed |Added Status|ASSIGNED|NEW Component|bootstrap

[Bug c++/77772] Segmentation fault when running an application with gdb

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=2 --- Comment #7 from Jose.DiazdeGrenu at digi dot com --- Seems like this has been fixed in gdb 7.11. Could you point to the commit that fixes it? Has it been backported to gdb 7.9?

[Bug sanitizer/79944] asan: incorrect instrumentation of atomic operations

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79944 --- Comment #6 from Dmitry Vyukov --- Just build kernel with it. Boots fine and sustains some load now. Did not do any positive tests, though. Thanks for the quick fix!

[Bug fortran/79886] [5/6/7 Regression] ICE in pp_format, at pretty-print.c:681

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79886 Jakub Jelinek changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last reconfirmed|

[Bug sanitizer/79944] asan: incorrect instrumentation of atomic operations

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79944 Jakub Jelinek changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last reconfirmed|

[Bug bootstrap/79956] [7 Regression] many new -Wmaybe-uninitialized warnings with bootstrap-O3

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79956 --- Comment #3 from Markus Trippelsdorf --- Testcase that only warns with -O3 int a, b, c; void fn1() { int d[1]; int e, n = a; for (; 0; n++) ; c = 1; while (c) { if (a) for (;;) ; while (d[0]) { e -=

[Bug bootstrap/79956] [7 Regression] many new -Wmaybe-uninitialized warnings with bootstrap-O3

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79956 --- Comment #2 from Markus Trippelsdorf --- Created attachment 40922 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40922=edit unreduced testcase

[Bug tree-optimization/79943] Loop splitting breaks with loops of pointer type

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79943 --- Comment #1 from Andrew Haley --- Author: aph Date: Wed Mar 8 11:35:23 2017 New Revision: 245974 URL: https://gcc.gnu.org/viewcvs?rev=245974=gcc=rev Log: 2017-03-08 Andrew Haley PR tree-optimization/79943

[Bug c++/79957] New: [C++] Zero-length array function parameters in templates should cause warning/substituion failure in pedantic mode

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79957 Bug ID: 79957 Summary: [C++] Zero-length array function parameters in templates should cause warning/substituion failure in pedantic mode Product: gcc Version:

[Bug c++/79900] [5/6/7 Regression] ICE in strip_typedefs, at cp/tree.c:1554

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79900 Marek Polacek changed: What|Removed |Added CC||mpolacek at gcc dot gnu.org --- Comment

  1   2   >