[Bug target/114036] Test failure of gcov-14.c on darwin

2024-04-29 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114036 Iain Sandoe changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Bug target/114036] Test failure of gcov-14.c on darwin

2024-04-29 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114036 --- Comment #8 from GCC Commits --- The releases/gcc-11 branch has been updated by Iain D Sandoe : https://gcc.gnu.org/g:5feeb2ddc93de85dffd7d52119189cd63bccd40f commit r11-11405-g5feeb2ddc93de85dffd7d52119189cd63bccd40f Author: Iain Sandoe

[Bug target/114036] Test failure of gcov-14.c on darwin

2024-04-21 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114036 --- Comment #7 from GCC Commits --- The releases/gcc-12 branch has been updated by Iain D Sandoe : https://gcc.gnu.org/g:ed046c2cc0f0a2d00cc77e5e9ce5d8f71e2278c6 commit r12-10379-ged046c2cc0f0a2d00cc77e5e9ce5d8f71e2278c6 Author: Iain Sandoe

[Bug target/114036] Test failure of gcov-14.c on darwin

2024-04-04 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114036 --- Comment #6 from GCC Commits --- The releases/gcc-13 branch has been updated by Iain D Sandoe : https://gcc.gnu.org/g:02a1d49da8f95a128d131747546921b67818d144 commit r13-8586-g02a1d49da8f95a128d131747546921b67818d144 Author: Iain Sandoe

[Bug target/114036] Test failure of gcov-14.c on darwin

2024-04-02 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114036 --- Comment #5 from Iain Sandoe --- fixed on trunk, needed on open branches.

[Bug target/114036] Test failure of gcov-14.c on darwin

2024-04-02 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114036 --- Comment #4 from GCC Commits --- The master branch has been updated by Iain D Sandoe : https://gcc.gnu.org/g:ad8e34eaa870608e2b07b4e7147e6ef2944bb8b5 commit r14-9747-gad8e34eaa870608e2b07b4e7147e6ef2944bb8b5 Author: Iain Sandoe Date:

[Bug target/114036] Test failure of gcov-14.c on darwin

2024-02-21 Thread fxcoudert at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114036 --- Comment #3 from Francois-Xavier Coudert --- There's only one symbol we care about here, and its name is known, so I'll make a patch with your suggestion and test it.

[Bug target/114036] Test failure of gcov-14.c on darwin

2024-02-21 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114036 --- Comment #2 from Iain Sandoe --- if there are lots of symbols that need to be undefined .. then one can use an undefined symbols file. Of course, it does not work if we do not know the symbol names at build-time.

[Bug target/114036] Test failure of gcov-14.c on darwin

2024-02-21 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114036 --- Comment #1 from Iain Sandoe --- yeah, there is a better way to do this with ld64 (and presumably dyld-ld), my guess is that this is an anachronism from the ld_classic (v1) days. We can tell the linker it's OK for a symbol to be undefined -

[Bug target/114036] Test failure of gcov-14.c on darwin

2024-02-21 Thread fxcoudert at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114036 Francois-Xavier Coudert changed: What|Removed |Added Status|UNCONFIRMED |NEW Target|