https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118975
--- Comment #1 from Nate Eldredge ---
I should have said, credit to StackOverflow user anol for finding this.
https://stackoverflow.com/questions/79457581/gcc-undef-leads-to-cannot-find-entry-symbol-start-defaulting-to-x/79457825#79457825
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118975
Bug ID: 118975
Summary: -undef is passed to the linker
Product: gcc
Version: 14.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: driver
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118927
--- Comment #6 from Nate Eldredge ---
After some brief digging, it seems like the problem is that
`cxx_printable_name_internal` can be called recursively by `lang_decl_name'
(via `announce_function'). This is bad because, with its static ring b
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118927
--- Comment #5 from Nate Eldredge ---
Oh, it's actually triggered by the compilation of a-foo.ii itself, but the
gcm.cache has to have previously been created.
The gcm.cache is too large to post as an attachment, but I can share it another
way
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118927
--- Comment #4 from Nate Eldredge ---
Note for testing that the compiler doesn't crash when compiling only
bits/std.cc, or when a-std.ii and a-foo.ii are concatenated into a single file.
It seems to be important that they are passed as separate
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118927
--- Comment #3 from Nate Eldredge ---
Created attachment 60527
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=60527&action=edit
stderr output from compilation
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118927
--- Comment #2 from Nate Eldredge ---
Created attachment 60526
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=60526&action=edit
Preprocessor output for std.cc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118927
--- Comment #1 from Nate Eldredge ---
Created attachment 60525
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=60525&action=edit
Preprocessor output for foo.cc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118927
Bug ID: 118927
Summary: "double free detected in tcache 2" with import std and
-Q
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
Pri
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117742
Bug ID: 117742
Summary: Inefficient code for __builtin_clear_padding
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tre
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104928
--- Comment #7 from Nate Eldredge ---
@Jonathan: Done,
https://gcc.gnu.org/pipermail/gcc-patches/2023-December/640119.html (sorry, may
not be linked to original threads).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104928
--- Comment #5 from Nate Eldredge ---
Oh wait, disregard that last, I realized that I only applied one of the two
patches. Let me try again.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104928
--- Comment #4 from Nate Eldredge ---
@Jonathan: I think that patch set is on the right track, but it has some other
serious bugs. For one, __atomic_wait_address calls __detail::__wait_impl with
__args._M_old uninitialized (g++ -O3 -Wall catche
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104928
--- Comment #2 from Nate Eldredge ---
This bug is still present. Tested and reproduced with g++ 13.1.0 (Ubuntu
package), and by inspection of the source code, it's still in the trunk as
well.
Encountered on StackOverflow:
https://stackoverflow
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110780
Bug ID: 110780
Summary: aarch64 NEON redundant displaced ld3
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30527
Nate Eldredge changed:
What|Removed |Added
CC||nate at thatsmathematics dot
com
--- Co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104110
Bug ID: 104110
Summary: AArch64 unnecessary use of call-preserved register
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Componen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104039
Bug ID: 104039
Summary: AArch64 Redundant instruction moving general to vector
register
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97473
--- Comment #2 from Nate Eldredge ---
Possibly related to bug 84877 ?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97473
Bug ID: 97473
Summary: Spilled function parameters not aligned properly on
multiple non-x86 targets
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Keywords: wro
20 matches
Mail list logo