https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109577
--- Comment #9 from nightstrike ---
(In reply to David Malcolm from comment #8)
> Should be fixed for GCC 13 (for the upcoming GCC 13.3) by the above patches.
Did you miss my comment #5 highlighting the need to adjust the declaration of
malloc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110014
--- Comment #6 from nightstrike ---
(In reply to David Malcolm from comment #5)
> Should be fixed for GCC 13 (for the upcoming GCC 13.3) by the above patch.
Did you miss my comment #3 that highlighted the problem due to assuming that
size_t ==
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114534
Bug ID: 114534
Summary: Feature request: extend VLA support in C++
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108644
nightstrike changed:
What|Removed |Added
CC||nightstrike at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43613
--- Comment #10 from nightstrike ---
Patch thread started here:
https://gcc.gnu.org/pipermail/gcc-patches/2024-February/644674.html
https://inbox.sourceware.org/gcc-patches/4700e066-1b50-4e7b-92f7-d8c33a330...@gmail.com/
and ended with this sol
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105755
--- Comment #6 from nightstrike ---
(In reply to nightstrike from comment #5)
> If I open your godbolt links, they aren't using a Windows target compiler,
> so they aren't exercising an LLP64 target.
For instance:
https://godbolt.org/z/4Mx96Wjv
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105755
--- Comment #5 from nightstrike ---
(In reply to David Malcolm from comment #4)
> Looks like this was fixed sometime in GCC 13; resolving as WORKSFORME.
>
> Feel free to reopen if you have a reproducer that triggers on a more recent
> GCC.
The
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111022
--- Comment #35 from nightstrike ---
(In reply to anlauf from comment #34)
> Are you sure that it finds the right new libgfortran?
Good call. I did a make install first and re-ran it, and they all pass now.
Sorry for the noise, this is an unf
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111022
--- Comment #33 from nightstrike ---
I modified the test further to just print which ones would have called stop.
Almost, but not all, do:
stop 2
stop 3
stop 4
stop 7
stop 8
stop 9
stop 10
stop 11
stop 12
stop 13
stop 15
stop 20
s
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111022
--- Comment #32 from nightstrike ---
(In reply to anlauf from comment #31)
> (In reply to nightstrike from comment #30)
> > (In reply to GCC Commits from comment #29)
> > > * gfortran.dg/pr111022.f90: New test.
> >
> > This new test
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111022
nightstrike changed:
What|Removed |Added
CC||nightstrike at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113624
nightstrike changed:
What|Removed |Added
Known to fail||11.3.0, 12.2.0, 13.0, 14.0
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105755
nightstrike changed:
What|Removed |Added
CC||nightstrike at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109577
nightstrike changed:
What|Removed |Added
CC||nightstrike at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110014
nightstrike changed:
What|Removed |Added
CC||nightstrike at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113634
Bug ID: 113634
Summary: FAIL: gcc.dg/Wfree-nonheap-object-7.c, incorrect
declaration for calloc()
Product: gcc
Version: unknown
Status: UNCONFIRMED
Keywords: t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113633
Bug ID: 113633
Summary: FAIL: gcc.dg/bf-ms-attrib.c execution test, wrong size
for ms_struct
Product: gcc
Version: unknown
Status: UNCONFIRMED
Keywords: ABI, t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113631
Bug ID: 113631
Summary: FAIL: gcc.dg/pr7356.c, fix still fails with #pragma
Product: gcc
Version: unknown
Status: UNCONFIRMED
Keywords: diagnostic, testsuite-fail
Severi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113624
Bug ID: 113624
Summary: FAIL: g++.dg/ext/dllimport4.C, ICE on windows targets
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113591
Bug ID: 113591
Summary: FAIL: g++.dg/cpp0x/lambda/lambda-ice15.C
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113589
Bug ID: 113589
Summary: FAIL: experimental/filesystem/operations/absolute.cc
on Windows
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100058
nightstrike changed:
What|Removed |Added
CC||nightstrike at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113549
--- Comment #4 from nightstrike ---
(In reply to Andrew Pinski from comment #3)
> Either the stack size or the stack alignment issue.
>
> I am suspecting a stack alignement issue.
Possibly related: PR110273
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113548
--- Comment #3 from nightstrike ---
Seeing as how this is a testsuite issue, it seems that the crash in the same
location applies to the following:
FAIL: gcc.dg/vect/vect-ifcvt-19.c (internal compiler error: in build2, at
tree.cc:5097)
FAIL: gc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113549
--- Comment #2 from nightstrike ---
Test 16e uses double instead of float, which also crashes.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113549
--- Comment #1 from nightstrike ---
Created attachment 57188
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57188&action=edit
Failing source for easier copying
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113549
Bug ID: 113549
Summary: float simd crash on windows in
gcc.dg/vect/vect-simd-clone-16b.c
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113548
Bug ID: 113548
Summary: ICE vect-ifcvt-19 in build2, at tree.cc:5097
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tre
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107603
nightstrike changed:
What|Removed |Added
CC||nightstrike at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59425
nightstrike changed:
What|Removed |Added
CC||nightstrike at gmail dot com
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113516
Bug ID: 113516
Summary: POLLPRI redefined on windows building ada
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: ada
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65257
--- Comment #2 from nightstrike ---
I should clarify that I tested this with mingw-w64, not mingw.org where the bug
was originally reported.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65257
nightstrike changed:
What|Removed |Added
CC||nightstrike at gmail dot com
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43613
nightstrike changed:
What|Removed |Added
CC||nightstrike at gmail dot com
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110167
Bug ID: 110167
Summary: excessive compile time when optimizing std::to_array
Product: gcc
Version: 13.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Comp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69639
--- Comment #18 from nightstrike ---
(In reply to nightstrike from comment #9)
> This affects 8-trunk on x86_64 cygwin, as well. The default size of the
> stack for cc1 is:
>
> $ peflags -x /tmp/b2/gcc/cc1.exe
> /tmp/b2/gcc/cc1.exe: stack reser
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108942
Bug ID: 108942
Summary: ICE in build2, at tree.c: 5096 for
gcc/testsuite/gcc.dg/torture/ssa-fre-7.c:23:3
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severit
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83286
nightstrike changed:
What|Removed |Added
CC||nightstrike at gmail dot com
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90458
--- Comment #8 from nightstrike ---
FYI, this is the same as the failure in gcc/testsuite/gcc.dg/stack-check-16.c:
(running this under Wine)
during RTL pass: final
gcc.dg/stack-check-16.c:36:1: internal compiler error: in
i386_pe_seh_unwind_emi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108675
--- Comment #9 from nightstrike ---
I understand it's not ideal based on comment #6, but this fixes all the tests:
diff --git a/gcc/testsuite/gcc.c-torture/execute/builtins/lib/fprintf.c
b/gcc/testsuite/gcc.c-torture/execute/builtins/lib/fprint
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108709
--- Comment #1 from nightstrike ---
Perhaps these are separate bugs, but:
1) gcc.dg/analyzer/pipe-manpages.c will need similar improvements
2) gcc.dg/analyzer/pipe-void-return.c passes with an incorrect declaration for
pipe(), implying that we
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108709
Bug ID: 108709
Summary: FAIL: gcc.dg/analyzer/pipe-glibc.c
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: analyzer
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108708
Bug ID: 108708
Summary: __analyzer_dump_named_constant fails with derived
values
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Prio
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107602
--- Comment #2 from nightstrike ---
Better link(In reply to nightstrike from comment #1)
> Reverting 186d43a78e945ebe9fbe217fc341847af7f95d30 fixes this problem at
> least for me
Better link: r255433
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107602
nightstrike changed:
What|Removed |Added
CC||nightstrike at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108675
--- Comment #8 from nightstrike ---
(In reply to LIU Hao from comment #7)
> (In reply to nightstrike from comment #5)
> > (In reply to LIU Hao from comment #4)
> > > Does it make any sense to remove `#include ` from
> > > 'gcc.c-torture/execute/
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108675
--- Comment #5 from nightstrike ---
(In reply to LIU Hao from comment #4)
> Does it make any sense to remove `#include ` from
> 'gcc.c-torture/execute/builtins/lib/fprintf.c' ?
That will prevent the FILE type from existing, so the replacement f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108675
--- Comment #2 from nightstrike ---
(In reply to Richard Biener from comment #1)
> These tests are known to be a bit awkwardly implemented to check for
> optimizations done ...
How would you do it if you were writing the test today?
> There mi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108675
Bug ID: 108675
Summary: FAIL: gcc.c-torture/execute/builtins/*printf.c when
stdio.h includes definitions
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severit
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90826
nightstrike changed:
What|Removed |Added
CC||nightstrike at gmail dot com
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108427
Bug ID: 108427
Summary: bitfield tests fail with missing warnings
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: testsu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108408
Bug ID: 108408
Summary: libphobos: Support building on *-*-cygwin
Product: gcc
Version: 11.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: d
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108300
nightstrike changed:
What|Removed |Added
CC||nightstrike at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82028
nightstrike changed:
What|Removed |Added
CC||nightstrike at gmail dot com
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90256
nightstrike changed:
What|Removed |Added
CC||nightstrike at gmail dot com
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99794
--- Comment #3 from nightstrike ---
Hm, looks like it *IS* in 11. I was confused by the PR being open and the
version stating 11, thinking that it still wasn't applied. So the remaining
issues then are building on cygwin. But at least on a lin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99794
nightstrike changed:
What|Removed |Added
CC||nightstrike at gmail dot com
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108204
--- Comment #4 from nightstrike ---
(In reply to Richard Biener from comment #3)
> I'd suggest to add a dg-additional-options -fno-ms-extensions to the test
> then.
We certainly can (well, Jon can :P), but shouldn't the ms extensions ultimately
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108332
nightstrike changed:
What|Removed |Added
CC||10walls at gmail dot com,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108192
--- Comment #3 from nightstrike ---
Created attachment 54209
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54209&action=edit
Patch to change printf to puts so it works everywhere
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108152
nightstrike changed:
What|Removed |Added
CC||10walls at gmail dot com
--- Comment #3 f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107974
nightstrike changed:
What|Removed |Added
CC||nightstrike at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108150
nightstrike changed:
What|Removed |Added
CC||10walls at gmail dot com
--- Comment #2 f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102993
nightstrike changed:
What|Removed |Added
CC||nightstrike at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103327
nightstrike changed:
What|Removed |Added
CC||nightstrike at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100427
--- Comment #11 from nightstrike ---
Possible duplicate of PR39947
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100427
nightstrike changed:
What|Removed |Added
CC||nightstrike at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106395
nightstrike changed:
What|Removed |Added
CC||nightstrike at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108210
nightstrike changed:
What|Removed |Added
CC||i.nixman at autistici dot org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108207
--- Comment #1 from nightstrike ---
Ah, Andrew, before you beat me to it... this doesn't ICE if you pass
-fno-ms-extensions, and it does ICE on Linux if you pass -fms-extensions
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108207
Bug ID: 108207
Summary: ICE in testcase g++.dg/other/ptrmem8.C on mingw
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108204
--- Comment #2 from nightstrike ---
(In reply to Andrew Pinski from comment #1)
> Try with -fno-ms-extensions or try -fms-extension on Linux.
Hey, we have a winner! -fms-extension on Linux results in the bad error, and
-fno-ms-extensions on mi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108204
Bug ID: 108204
Summary: pr84973-2.C fails with wrong error on mingw
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108203
Bug ID: 108203
Summary: Format string checking with __USE_MINGW_ANSI_STDIO
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Componen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101854
--- Comment #11 from nightstrike ---
(In reply to Martin Sebor from comment #9)
> Fixed for GCC 12. The patch is far too intrusive to backport but the
> following should fix the problem in GCC 11:
Would you mind applying it to 11? Thanks!
Al
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108192
--- Comment #2 from nightstrike ---
(In reply to H.J. Lu from comment #1)
> Since Windows doesn't support IBT, this test can be limited to Linux.
I don't know what IBT is, but if I change the two printf's to puts(), the tests
pass. So, maybe t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108192
Bug ID: 108192
Summary: g++.dg/cet-notrack-1.C searching for wrong function on
mingw
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108190
--- Comment #5 from nightstrike ---
Created attachment 54138
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54138&action=edit
avx512vl-pr54700-1b.s
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108190
--- Comment #4 from nightstrike ---
Created attachment 54137
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54137&action=edit
avx512vl-pr54700-1a.s
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108190
--- Comment #3 from nightstrike ---
Created attachment 54136
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54136&action=edit
avx2-pr54700-1.s
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108190
--- Comment #1 from nightstrike ---
Created attachment 54135
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54135&action=edit
avx-pr54700-1.s
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108190
Bug ID: 108190
Summary: Various testsuite asm fails
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: testsuite
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108152
--- Comment #2 from nightstrike ---
(In reply to Andrew Pinski from comment #1)
> { dg-options "" }
That would remove every option, no? Do others matter, like -pedantic, or
whatever else is there?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108150
--- Comment #1 from nightstrike ---
Ok, that was dumb.. WINT_MAX is wide int max... hah. So maybe test for
__CYGWIN__ || __WIN32__
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108161
Bug ID: 108161
Summary: gcc.dg/ipa/pr96040.c fails with incorrect size_t
assumption (snprintf, strspn)
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108160
--- Comment #1 from nightstrike ---
It looks like the other testsuite changes (attr-8.c, the objc/c++ tests, etc.)
should be evaluated and ported over also, so this isn't a complete fix.
Alternatively, maybe this would scale better in the futur
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108160
Bug ID: 108160
Summary: gcc.dg/format/ms_attr-3.c testsuite failure, missed
update from r9-4163-g1d24950977c730
Product: gcc
Version: unknown
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108159
--- Comment #1 from nightstrike ---
Andrew pointed out that this is the better fix, and it does indeed work:
diff --git a/gcc/testsuite/gcc.dg/format/ms-format2.c
b/gcc/testsuite/gcc.dg/format/ms-format2.c
index 5c950522a7c..9d21d108642 100644
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108159
Bug ID: 108159
Summary: gcc.dg/format/ms-format2.c fails due to warning
message change
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108152
Bug ID: 108152
Summary: gcc.dg/pr71558.c fails for LLP64
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: testsuite
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108151
Bug ID: 108151
Summary: gcc.dg/pr64536.c stores pointers in a long, broken for
llp64
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108150
Bug ID: 108150
Summary: gcc.dg/attr-aligned.c fails with incorrect max
alignment
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
P
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107754
Bug ID: 107754
Summary: Confusing -Warray-bounds warning with strcpy
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107531
--- Comment #2 from nightstrike ---
It looks like you're right. The root cause of the problem is that in my
non-reduced case, I didn't have a copy constructor, but I had a non-default
destructor that was releasing resources twice. So it's clea
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107531
Bug ID: 107531
Summary: List of references calls destructors, add warning?
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Compon
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107463
Bug ID: 107463
Summary: Better error request for invalid initializer list of
aggregate
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103996
Bug ID: 103996
Summary: Enhancement: Better diagnostic for invalid reuse of a
function name
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102060
Bug ID: 102060
Summary: -Wprio-ctor-dtor underlines the wrong part of the
source line
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102052
Bug ID: 102052
Summary: analyser testsuite failures with LLP64 model
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: ana
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102010
Bug ID: 102010
Summary: ICE in stack-check-8.c in i386_pe_seh_unwind_emit
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component
1 - 100 of 105 matches
Mail list logo