https://gcc.gnu.org/bugzilla/show_bug.cgi?id=07
--- Comment #13 from Alex Henrie ---
I should clarify that I was testing with GCC 12.2. It turns out that GCC 12.3
does not crash, and I have now confirmed that the patch from comment #5 applied
to GCC 12.3 fixes
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=07
--- Comment #12 from Alex Henrie ---
Created attachment 56687
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56687=edit
Minimal example to reproduce the crash
Here's a minimal example that crashes on MinGW 12 with -m32 -mavx512f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=07
--- Comment #11 from Alex Henrie ---
Well, this is interesting: Unpatched MinGW 12 crashes in the same way if I set
both -march=native and -mpreferred-stack-boundary=2. So the problem is not the
patch itself, it's just that the patch revealed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=07
Alex Henrie changed:
What|Removed |Added
CC||alexhenrie24 at gmail dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111056
--- Comment #3 from Alex Henrie ---
By the way, thanks for pointing out that using constexpr suppresses the warning
on GCC. Although Clang does not support constexpr in C yet, it is interesting
that Clang is smart enough to not warn about a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111056
Alex Henrie changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111056
Bug ID: 111056
Summary: Missing -Wsign-compare warning with enum values
Product: gcc
Version: 13.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110426
--- Comment #4 from Alex Henrie ---
I tried out your changes and the warnings look great now. Thank you!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110426
Bug ID: 110426
Summary: Missing buffer overflow warning with function pointer
that has the alloc_size attribute
Product: gcc
Version: 13.1.1
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66618
--- Comment #9 from Alex Henrie ---
(In reply to Andrew Pinski from comment #7)
> (In reply to Alex Henrie from comment #6)
> > This wasn't fixed properly, or it was broken again before the release of GCC
> > 8.1: In GCC 8.1 and later no warning
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66618
Alex Henrie changed:
What|Removed |Added
CC||alexhenrie24 at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108476
--- Comment #3 from Alex Henrie ---
(In reply to Andrew Pinski from comment #1)
> Note the warning should really be split into two different options. One for
> the return type of the declaration and one for the missing return in
> non-void
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108476
Bug ID: 108476
Summary: Please turn -Wreturn-type on by default for C
Product: gcc
Version: 12.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105677
Bug ID: 105677
Summary: Calling strlen on a string constant is optimized out,
but calling wcslen on a string constant is not
Product: gcc
Version: 12.1.1
Status:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65403
--- Comment #15 from Alex Henrie ---
Nicholas Guriev also sent a patch for this issue:
https://gcc.gnu.org/pipermail/gcc-patches/2021-June/573774.html
15 matches
Mail list logo
