[Bug preprocessor/120421] -save-temps affects diagnostic position

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120421 --- Comment #6 from nightstrike --- (In reply to Andrew Pinski from comment #2) > Dup. > > *** This bug has been marked as a duplicate of bug 95695 *** Respectfully, I don't think this is a duplicate of a bug that was resolved as invalid. Tha

[Bug c++/120421] New: -save-temps affects diagnostic position

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120421 Bug ID: 120421 Summary: -save-temps affects diagnostic position Product: gcc Version: 14.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++

[Bug libstdc++/120390] Request to improve error with private destructor

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120390 --- Comment #6 from nightstrike --- (In reply to Jonathan Wakely from comment #5) > (In reply to nightstrike from comment #3) > > I know it isn't a bug, > > You're missing the point. It *is* a bug if the diagnostic is bad. My point > is that it

[Bug c++/120390] Request to improve error with private destructor

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120390 --- Comment #3 from nightstrike --- I know it isn't a bug, it's bad code that the compiler is correctly erroring out on. My point is that the original error message was spot on perfect in highlighting the issue being that the destructor was pri

[Bug c++/120390] Request to improve error with private destructor

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120390 --- Comment #1 from nightstrike --- (In reply to nightstrike from comment #0) > either 1) I was missing private:, "missing public:", obviously

[Bug c++/120390] New: Request to improve error with private destructor

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120390 Bug ID: 120390 Summary: Request to improve error with private destructor Product: gcc Version: 14.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Componen

[Bug c/119891] New: Incorrect suggestion for sizeof and printf

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119891 Bug ID: 119891 Summary: Incorrect suggestion for sizeof and printf Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c

[Bug testsuite/119791] FAIL: gcc.dg/stack-check-10.c on Windows

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119791 --- Comment #1 from nightstrike --- Created attachment 61102 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61102&action=edit RTL on linux

[Bug testsuite/119791] FAIL: gcc.dg/stack-check-10.c on Windows

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119791 --- Comment #3 from nightstrike --- Created attachment 61104 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61104&action=edit asm on Linux

[Bug testsuite/119791] FAIL: gcc.dg/stack-check-10.c on Windows

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119791 --- Comment #2 from nightstrike --- Created attachment 61103 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61103&action=edit asm on Windows

[Bug testsuite/119791] New: FAIL: gcc.dg/stack-check-10.c on Windows

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119791 Bug ID: 119791 Summary: FAIL: gcc.dg/stack-check-10.c on Windows Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: testsui

[Bug c++/86273] confusing diagnostic for member-declaration with missing identifier

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86273 nightstrike changed: What|Removed |Added Known to work||13.1.0 Known to fail|

[Bug testsuite/119789] New: FAIL: gcc.dg/20021029-1.c on Windows

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119789 Bug ID: 119789 Summary: FAIL: gcc.dg/20021029-1.c on Windows Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: testsuite

[Bug target/119765] FAIL: gcc.target/i386/amd64-abi-9.c on Windows

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119765 --- Comment #6 from nightstrike --- Patch posted: https://gcc.gnu.org/pipermail/gcc-patches/2025-April/680856.html

[Bug target/119765] FAIL: gcc.target/i386/amd64-abi-9.c on Windows

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119765 --- Comment #4 from nightstrike --- Ah, I think I understand better. It's not the AMD64 ABI saying to pass the register count in EAX, it's the SysV or whatever ABI saying to do it, and the Windows ABI says to do something else. So really instead

[Bug target/119765] FAIL: gcc.target/i386/amd64-abi-9.c on Windows

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119765 --- Comment #3 from nightstrike --- Is this a case of "skip windows", or a case of "skip targets with/without feature X"? Also, I'm a little surprised, as based on the name of the test, I would think it was testing a feature of the cpu type, no

[Bug c/119765] New: FAIL: gcc.target/i386/amd64-abi-9.c on Windows

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119765 Bug ID: 119765 Summary: FAIL: gcc.target/i386/amd64-abi-9.c on Windows Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c

[Bug ipa/117432] [12/13 Regression] IPA ICF disregards types of variadic arguments since r10-4643-ga37f58f506e436

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117432 --- Comment #19 from nightstrike --- (In reply to Sam James from comment #17) > (In reply to nightstrike from comment #16) > > I think you've either made an error and tested with the wrong GCC, or it > needs its own bug. In C23, which is the de

[Bug c/119660] New: builtin functions erroneously suggested as originating in system headers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119660 Bug ID: 119660 Summary: builtin functions erroneously suggested as originating in system headers Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: norma

[Bug c/119658] New: Better support for freestanding env on Windows

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119658 Bug ID: 119658 Summary: Better support for freestanding env on Windows Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c

[Bug ipa/117432] [12/13 Regression] IPA ICF disregards types of variadic arguments since r10-4643-ga37f58f506e436

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117432 nightstrike changed: What|Removed |Added CC||nightstrike at gmail dot com --- Comment

[Bug cobol/119414] cobol driver unconditionally adds platform-specific command line options.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119414 nightstrike changed: What|Removed |Added CC||nightstrike at gmail dot com --- Comment

[Bug preprocessor/119438] New: More descriptive warning desired: '#' is not followed by a macro parameter

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119438 Bug ID: 119438 Summary: More descriptive warning desired: '#' is not followed by a macro parameter Product: gcc Version: 14.2.1 Status: UNCONFIRMED Severity: n

[Bug testsuite/108152] gcc.dg/pr71558.c fails for LLP64

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108152 --- Comment #4 from nightstrike --- >From Andrew on IRC: use __extension__ before __SIZE_TYPE__ This should alleviate the pedantic warnings while (I believe) not invalidating the point of the test.

[Bug c/87950] GCC warns about reaching end of non-void function when all switch cases are completely handled

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87950 nightstrike changed: What|Removed |Added CC||nightstrike at gmail dot com --- Comment #

[Bug analyzer/109577] -Wanalyzer-allocation-size mishandles __builtin_mul_overflow

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

[Bug analyzer/110014] -Wanalyzer-allocation-size mishandles realloc (..., .... * sizeof (object))

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 ==

[Bug c++/114534] New: Feature request: extend VLA support in C++

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++

[Bug other/108644] Format string warnings related to longs under MigW-W64/MSYS2 on Windows 10

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108644 nightstrike changed: What|Removed |Added CC||nightstrike at gmail dot com --- Comment

[Bug target/43613] Some architecture-dependent codes

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

[Bug analyzer/105755] -Wanalyzer-null-dereference regression compiling Emacs

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

[Bug analyzer/105755] -Wanalyzer-null-dereference regression compiling Emacs

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

[Bug libfortran/111022] ES0.0E0 format gave ES0.dE0 output with d too high.

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

[Bug libfortran/111022] ES0.0E0 format gave ES0.dE0 output with d too high.

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

[Bug libfortran/111022] ES0.0E0 format gave ES0.dE0 output with d too high.

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

[Bug libfortran/111022] ES0.0E0 format gave ES0.dE0 output with d too high.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111022 nightstrike changed: What|Removed |Added CC||nightstrike at gmail dot com --- Comment

[Bug c++/113624] FAIL: g++.dg/ext/dllimport4.C, ICE on windows targets

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

[Bug analyzer/105755] -Wanalyzer-null-dereference regression compiling Emacs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105755 nightstrike changed: What|Removed |Added CC||nightstrike at gmail dot com --- Comment

[Bug analyzer/109577] -Wanalyzer-allocation-size mishandles __builtin_mul_overflow

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109577 nightstrike changed: What|Removed |Added CC||nightstrike at gmail dot com --- Comment

[Bug analyzer/110014] -Wanalyzer-allocation-size mishandles realloc (..., .... * sizeof (object))

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110014 nightstrike changed: What|Removed |Added CC||nightstrike at gmail dot com --- Comment

[Bug testsuite/113634] New: FAIL: gcc.dg/Wfree-nonheap-object-7.c, incorrect declaration for calloc()

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

[Bug target/113633] New: FAIL: gcc.dg/bf-ms-attrib.c execution test, wrong size for ms_struct

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

[Bug c/113631] New: FAIL: gcc.dg/pr7356.c, fix still fails with #pragma

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

[Bug c++/113624] New: FAIL: g++.dg/ext/dllimport4.C, ICE on windows targets

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

[Bug c++/113591] New: FAIL: g++.dg/cpp0x/lambda/lambda-ice15.C

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++

[Bug libstdc++/113589] New: FAIL: experimental/filesystem/operations/absolute.cc on Windows

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

[Bug target/100058] -Wpadded is inconsistent using -mms-bitfields

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100058 nightstrike changed: What|Removed |Added CC||nightstrike at gmail dot com --- Comment

[Bug target/113549] float simd crash on windows in gcc.dg/vect/vect-simd-clone-16b.c

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

[Bug testsuite/113548] gcc.dg/vect/vect-ifcvt-19.c ICEs on LLP64 target

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

[Bug target/113549] float simd crash on windows in gcc.dg/vect/vect-simd-clone-16b.c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113549 --- Comment #2 from nightstrike --- Test 16e uses double instead of float, which also crashes.

[Bug target/113549] float simd crash on windows in gcc.dg/vect/vect-simd-clone-16b.c

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

[Bug target/113549] New: float simd crash on windows in gcc.dg/vect/vect-simd-clone-16b.c

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

[Bug tree-optimization/113548] New: ICE vect-ifcvt-19 in build2, at tree.cc:5097

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

[Bug libstdc++/107603] checking for ld that supports -Wl,--gc-sections... configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES. for i686-w64-mingw32 target at canadian compilation

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107603 nightstrike changed: What|Removed |Added CC||nightstrike at gmail dot com --- Comment

[Bug target/59425] ICE - seg fault building ISL on Windows

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59425 nightstrike changed: What|Removed |Added CC||nightstrike at gmail dot com --- Comment #

[Bug ada/113516] New: POLLPRI redefined on windows building ada

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

[Bug libstdc++/65257] cin not working with empty string when _GLIBCXX_DEBUG is defined on Windows

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.

[Bug libstdc++/65257] cin not working with empty string when _GLIBCXX_DEBUG is defined on Windows

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65257 nightstrike changed: What|Removed |Added CC||nightstrike at gmail dot com --- Comment #

[Bug target/43613] Some architecture-dependent codes

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43613 nightstrike changed: What|Removed |Added CC||nightstrike at gmail dot com --- Comment #

[Bug libstdc++/110167] New: excessive compile time when optimizing std::to_array

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

[Bug target/69639] [10/11/12/13 Regression] FAIL: gcc.c-torture/compile/limits-exprparen.c

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

[Bug c/108942] New: ICE in build2, at tree.c: 5096 for gcc/testsuite/gcc.dg/torture/ssa-fre-7.c:23:3

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

[Bug middle-end/83286] internal compiler error: Illegal instruction

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83286 nightstrike changed: What|Removed |Added CC||nightstrike at gmail dot com --- Comment #

[Bug target/90458] [10/11/12/13 Regression] mingw64: ICE in i386_pe_seh_unwind_emit, at config/i386/winnt.c:1258 with -fstack-clash-protection

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

[Bug testsuite/108675] FAIL: gcc.c-torture/execute/builtins/*printf.c when stdio.h includes definitions

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

[Bug testsuite/108709] FAIL: gcc.dg/analyzer/pipe-glibc.c

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

[Bug analyzer/108709] New: FAIL: gcc.dg/analyzer/pipe-glibc.c

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

[Bug analyzer/108708] New: __analyzer_dump_named_constant fails with derived values

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

[Bug testsuite/107602] dump-noaddr testcases fail when running the testsuite with already built installed toolchain

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

[Bug testsuite/107602] dump-noaddr testcases fail when running the testsuite with already built installed toolchain

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107602 nightstrike changed: What|Removed |Added CC||nightstrike at gmail dot com --- Comment

[Bug testsuite/108675] FAIL: gcc.c-torture/execute/builtins/*printf.c when stdio.h includes definitions

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/

[Bug testsuite/108675] FAIL: gcc.c-torture/execute/builtins/*printf.c when stdio.h includes definitions

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

[Bug testsuite/108675] FAIL: gcc.c-torture/execute/builtins/*printf.c when stdio.h includes definitions

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

[Bug testsuite/108675] New: FAIL: gcc.c-torture/execute/builtins/*printf.c when stdio.h includes definitions

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

[Bug target/90826] Weak symbol does not work reliably on windows

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90826 nightstrike changed: What|Removed |Added CC||nightstrike at gmail dot com --- Comment #

[Bug testsuite/108427] New: bitfield tests fail with missing warnings

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

[Bug d/108408] New: libphobos: Support building on *-*-cygwin

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

[Bug middle-end/108300] `abort()` macro cause bootstrap failure on *-w64-mingw32

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108300 nightstrike changed: What|Removed |Added CC||nightstrike at gmail dot com --- Comment

[Bug target/82028] Windows x86_64 should not pass float aggregates in xmm

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82028 nightstrike changed: What|Removed |Added CC||nightstrike at gmail dot com --- Comment #

[Bug target/90256] Optimizer with interrupt routines

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90256 nightstrike changed: What|Removed |Added CC||nightstrike at gmail dot com --- Comment #

[Bug d/99794] libphobos: Support building on *-*mingw*

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

[Bug d/99794] libphobos: Support building on *-*mingw*

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99794 nightstrike changed: What|Removed |Added CC||nightstrike at gmail dot com --- Comment #

[Bug testsuite/108204] pr84973-2.C fails with wrong error on mingw

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

[Bug libstdc++/108332] dynamic link libstdc++ with win32 thread model's gcc for windows native toolchain would cause .rdata_r: section below image base

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108332 nightstrike changed: What|Removed |Added CC||10walls at gmail dot com,

[Bug testsuite/108192] g++.dg/cet-notrack-1.C searching for wrong function on mingw

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

[Bug testsuite/108152] gcc.dg/pr71558.c fails for LLP64

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108152 nightstrike changed: What|Removed |Added CC||10walls at gmail dot com --- Comment #3 f

[Bug preprocessor/107974] compiler can't find source file in path that is longer than 255 characters

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107974 nightstrike changed: What|Removed |Added CC||nightstrike at gmail dot com --- Comment

[Bug testsuite/108150] gcc.dg/attr-aligned.c fails with incorrect max alignment

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108150 nightstrike changed: What|Removed |Added CC||10walls at gmail dot com --- Comment #2 f

[Bug target/102993] -fcf-protection=full produces segfaulting code when targeting 32-bit x86 (i686)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102993 nightstrike changed: What|Removed |Added CC||nightstrike at gmail dot com --- Comment

[Bug target/103327] Do not search MINGW in the search dir

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103327 nightstrike changed: What|Removed |Added CC||nightstrike at gmail dot com --- Comment

[Bug bootstrap/100427] canadian compile for mingw-w64 copies the wrong dlls for mingw-w64 multilibs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100427 --- Comment #11 from nightstrike --- Possible duplicate of PR39947

[Bug bootstrap/100427] canadian compile for mingw-w64 copies the wrong dlls for mingw-w64 multilibs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100427 nightstrike changed: What|Removed |Added CC||nightstrike at gmail dot com --- Comment

[Bug c++/106395] [12/13 regression] [mingw] "redeclared without dllimport attribute: previous dllimport ignored" on C++ friend since r12-299-ga0fdff3cf33f72

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106395 nightstrike changed: What|Removed |Added CC||nightstrike at gmail dot com --- Comment

[Bug libstdc++/108210] error: 'mutex' does not name a type; did you mean 'minutes'? for x86_64-w64-mingw32 target with win32 thread model

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108210 nightstrike changed: What|Removed |Added CC||i.nixman at autistici dot org,

[Bug c++/108207] ICE in testcase g++.dg/other/ptrmem8.C on mingw

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

[Bug c++/108207] New: ICE in testcase g++.dg/other/ptrmem8.C on mingw

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:

[Bug c++/108204] pr84973-2.C fails with wrong error on mingw

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

[Bug c++/108204] New: pr84973-2.C fails with wrong error on mingw

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++

[Bug c++/108203] New: Format string checking with __USE_MINGW_ANSI_STDIO

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

[Bug tree-optimization/101854] [11 Regression] Invalid warning -Wstringop-overflow wrong argument

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

  1   2   >