[Bug target/114839] g++-linked FreeBSD static binaries abort upon exception

2024-04-24 Thread emaste at freebsd dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114839 --- Comment #4 from Ed Maste --- Thanks - 54568 adds some good context. Based on that I think it may that frame registration calls are not present in the FreeBSD crt bits used for static binaries, which could explain the differences in OSes. We

[Bug target/114839] g++-linked FreeBSD static binaries abort upon exception

2024-04-24 Thread emaste at freebsd dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114839 --- Comment #3 from Ed Maste --- (In reply to Andrew Pinski from comment #2) > Is it the case that unwinder from LLVM needs a .eh_frame_hdr for static > binaries while GCC's libgcc one does not? That's possible, but in the investigation in the

[Bug driver/114839] New: g++-linked FreeBSD static binaries abort upon exception

2024-04-24 Thread emaste at freebsd dot org via Gcc-bugs
Priority: P3 Component: driver Assignee: unassigned at gcc dot gnu.org Reporter: emaste at freebsd dot org Target Milestone: --- When compiling and statically linking a binary on FreeBSD with GCC the EH_FRAME segment is omitted, and then libgcc's exception unw

[Bug driver/113218] New: gcc -pg fails on contemporary FreeBSD

2024-01-03 Thread emaste at freebsd dot org via Gcc-bugs
Assignee: unassigned at gcc dot gnu.org Reporter: emaste at freebsd dot org Target Milestone: --- FreeBSD retired _p profiled libraries in FreeBSD 14.0, so GCC specs need to be updated. Demonstrated below using the default FreeBSD devel/gcc port, but looking at gcc git I

[Bug target/66136] AArch64 geniterators.sh relies on GNU sed syntax, causing build failure on FreeBSD and probably Mac

2015-05-19 Thread emaste at freebsd dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66136 --- Comment #9 from Ed Maste --- (In reply to Szabolcs Nagy from comment #8) > the new awk version is supposed to produce the exact same output as the old > script with gnu sed. > > the pasted output fragment looks ok. Oops, I must have had a b

[Bug target/66136] AArch64 geniterators.sh relies on GNU sed syntax, causing build failure on FreeBSD and probably Mac

2015-05-19 Thread emaste at freebsd dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66136 --- Comment #7 from Ed Maste --- With the patch in comment 5 I get the same result with FreeBSD awk and GNU awk. The output is rather different to what the previous (sed) version of geniterators.sh produced, but that seems intentional. My output

[Bug target/66136] AArch64 geniterators.sh relies on GNU sed syntax, causing build failure on FreeBSD and probably Mac

2015-05-15 Thread emaste at freebsd dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66136 --- Comment #3 from Ed Maste --- > the posix standard does not seem to disallow \n in the replacement string so > i think freebsd sed should be fixed (or report the bug to the austingroup). I can't find language that specifies sed must interpre

[Bug target/66136] AArch64 geniterators.sh relies on GNU sed syntax, causing build failure on FreeBSD

2015-05-13 Thread emaste at freebsd dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66136 --- Comment #1 from Ed Maste --- It appears this comes from \n newlines in the replacement pattern - I can partially fix it by using an expression like: sed 's/(define_mode_iterator \([A-Za-z0-9_]*\) \([]\[A-Z0-9 \t]*\)/\ #define BUILTIN_\1(T

[Bug target/66136] New: AArch64 geniterators.sh relies on GNU sed syntax, causing build failure on FreeBSD

2015-05-13 Thread emaste at freebsd dot org
Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: emaste at freebsd dot org Target Milestone: --- Attempting to build an AArch64 target on FreeBSD fails with: In file included from ../../gcc/config/aarch64