[Bug target/108994] [13 Regression] LLVM JIT segfaults in libgcc after upgrading from gcc 12.2.1 to 13.0.1 since r13-2706-g6e80a1d164d1f9

2023-03-14 Thread tstellar at redhat dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108994 --- Comment #19 from Tom Stellard --- Thanks, Jakub. It looks like this is in fact an LLVM bug. I've posted a patch here that fixes my test case: https://reviews.llvm.org/D146067

[Bug target/108994] [13 Regression] LLVM JIT segfaults in libgcc after upgrading from gcc 12.2.1 to 13.0.1 since r13-2706-g6e80a1d164d1f9

2023-03-13 Thread tstellar at redhat dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108994 --- Comment #17 from Tom Stellard --- It looks like the issue is that the function classify_object_over_fdes() expects there to be a zero-length fde at the end of the fde array. It doesn't find one so it runs over the end of the array and segfa

[Bug target/108994] [13 Regression] LLVM JIT segfaults in libgcc after upgrading from gcc 12.2.1 to 13.0.1 since r13-2706-g6e80a1d164d1f9

2023-03-10 Thread tstellar at redhat dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108994 --- Comment #16 from Tom Stellard --- I looked into this a little more, and I think the s390x failures may be an LLVM bug. It's trying to JIT an X86 ELF file on s390x, and I think maybe the layout of the frames is different due to endianness.

[Bug target/108994] [13 Regression] LLVM JIT segfaults in libgcc after upgrading from gcc 12.2.1 to 13.0.1 since r13-2706-g6e80a1d164d1f9

2023-03-09 Thread tstellar at redhat dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108994 --- Comment #14 from Tom Stellard --- Better stack trace with line numbers as of gcc commit 288bc7b5d17511d1791899e4b2e3bf3489eb06dd. #0 0x016c96aa PrintStackTraceSignalHandler(void*) Signals.cpp:0:0 #1 0x016c9c18 SignalHandl

[Bug target/108994] [13 Regression] LLVM JIT segfaults in libgcc after upgrading from gcc 12.2.1 to 13.0.1 since r13-2706-g6e80a1d164d1f9

2023-03-09 Thread tstellar at redhat dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108994 --- Comment #13 from Tom Stellard --- (In reply to Tom Stellard from comment #12) > https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=6e80a1d164d1f9 is the first > bad commit. This commit also causes segfaults on s390x, but during frame registrati

[Bug target/108994] [13 Regression] LLVM JIT segfaults in libgcc after upgrading from gcc 12.2.1 to 13.0.1

2023-03-03 Thread tstellar at redhat dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108994 --- Comment #12 from Tom Stellard --- https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=6e80a1d164d1f9 is the first bad commit.

[Bug target/108994] [13 Regression] LLVM JIT segfaults in libgcc after upgrading from gcc 12.2.1 to 13.0.1

2023-03-03 Thread tstellar at redhat dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108994 --- Comment #11 from Tom Stellard --- (In reply to Jakub Jelinek from comment #10) > I'd start with verification if it is really libgcc, so don't recompile the > app, just try it against GCC 12.2.1 libgcc vs. 13.0.1. I confirmed it's libgcc. O

[Bug libgcc/108994] [13 Regression] LLVM JIT segfaults in libgcc after upgrading from gcc 12.2.1 to 13.0.1

2023-03-02 Thread tstellar at redhat dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108994 --- Comment #6 from Tom Stellard --- (In reply to Andrew Pinski from comment #5) > (In reply to Tom Stellard from comment #4) > > This test case was passing with older versions of LLVM/Clang + gcc-13.0.1, > > so I bisected it down to this commit

[Bug libgcc/108994] [13 Regression] LLVM JIT segfaults in libgcc after upgrading from gcc 12.2.1 to 13.0.1

2023-03-02 Thread tstellar at redhat dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108994 --- Comment #4 from Tom Stellard --- This test case was passing with older versions of LLVM/Clang + gcc-13.0.1, so I bisected it down to this commit: https://github.com/llvm/llvm-project/commit/6747fc07d1aa94e22622e278e5a02ba70675ac9b

[Bug libgcc/108994] [13 Regression] LLVM JIT segfaults in libgcc after upgrading from gcc 12.2.1 to 13.0.1

2023-03-02 Thread tstellar at redhat dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108994 --- Comment #2 from Tom Stellard --- $ gcc -v Using built-in specs. COLLECT_GCC=/usr/bin/gcc COLLECT_LTO_WRAPPER=/usr/libexec/gcc/aarch64-redhat-linux/13/lto-wrapper Target: aarch64-redhat-linux Configured with: ../configure --enable-bootstrap -

[Bug libgcc/108994] New: LLVM JIT segfaults in libgcc after upgrading from gcc 12.2.1 to 13.0.1

2023-03-02 Thread tstellar at redhat dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108994 Bug ID: 108994 Summary: LLVM JIT segfaults in libgcc after upgrading from gcc 12.2.1 to 13.0.1 Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal

[Bug lto/97524] Compiling with -flto=auto fails in make is not installed

2020-10-22 Thread tstellar at redhat dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97524 --- Comment #6 from Tom Stellard --- If I have make installed on my system, but am using something else (e.g. ninja) to build my project, will I still get parallel execution?

[Bug lto/97524] New: Compiling with -flto=auto fails in make is not installed

2020-10-21 Thread tstellar at redhat dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97524 Bug ID: 97524 Summary: Compiling with -flto=auto fails in make is not installed Product: gcc Version: 10.2.1 Status: UNCONFIRMED Severity: normal Prio