public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tstellar at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [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
Date: Thu, 09 Mar 2023 16:29:58 +0000	[thread overview]
Message-ID: <bug-108994-4-vI4s7yBTwh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108994-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108994

--- Comment #13 from Tom Stellard <tstellar at redhat dot com> ---
(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 registration
instead of frame deregistration:

PLEASE submit a bug report to https://github.com/llvm/llvm-project/issues/ and
include the crash backtrace.
Stack dump:
0.      Program arguments: /root/dev/llvm-project/build/bin/llvm-exegesis
-mtriple=x86_64-unknown-unknown -mcpu=x86-64 -mode=inverse_throughput
--benchmark-phase=assemble-measured-code -x86-disable-upper-sse-registers
-opcode-name=PBLENDVBrr0 -repetition-mode=loop
 #0 0x00000000016c96aa PrintStackTraceSignalHandler(void*) Signals.cpp:0:0
 #1 0x00000000016c9c18 SignalHandler(int) Signals.cpp:0:0
 #2 0x000003fff20dc488 (linux-vdso64.so.1+0x488)
 #3 0x000003ff8cc0dbe0 (/lib64/libgcc_s.so.1+0xdbe0)
 #4 0x000003ff8cc0e6ce __register_frame_info_bases
(/lib64/libgcc_s.so.1+0xe6ce)
 #5 0x0000000001ca1bb0 llvm::RTDyldMemoryManager::registerEHFrames(unsigned
char*, unsigned long, unsigned long)
(/root/dev/llvm-project/build/bin/llvm-exegesis+0x1ca1bb0)
 #6 0x0000000001cb1158 llvm::RuntimeDyldELF::registerEHFrames()
(/root/dev/llvm-project/build/bin/llvm-exegesis+0x1cb1158)
 #7 0x0000000001c923b6 llvm::MCJIT::finalizeLoadedModules()
(/root/dev/llvm-project/build/bin/llvm-exegesis+0x1c923b6)
 #8 0x0000000001c9367a
llvm::MCJIT::getFunctionAddress(std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char>> const&)
(/root/dev/llvm-project/build/bin/llvm-exegesis+0x1c9367a)
 #9 0x000000000171511a
llvm::exegesis::ExecutableFunction::ExecutableFunction(std::unique_ptr<llvm::LLVMTargetMachine,
std::default_delete<llvm::LLVMTargetMachine>>,
llvm::object::OwningBinary<llvm::object::ObjectFile>&&)
(/root/dev/llvm-project/build/bin/llvm-exegesis+0x171511a)
#10 0x00000000016e7ab4
llvm::exegesis::BenchmarkRunner::getRunnableConfiguration(llvm::exegesis::BenchmarkCode
const&, unsigned int, unsigned int, llvm::exegesis::SnippetRepetitor const&)
const (/root/dev/llvm-project/build/bin/llvm-exegesis+0x16e7ab4)
#11 0x0000000001077adc llvm::exegesis::benchmarkMain()
(/root/dev/llvm-project/build/bin/llvm-exegesis+0x1077adc)
#12 0x000000000107ab46 main
(/root/dev/llvm-project/build/bin/llvm-exegesis+0x107ab46)
#13 0x000003ff8ca34872 __libc_start_call_main (/lib64/libc.so.6+0x34872)
#14 0x000003ff8ca34950 __libc_start_main@GLIBC_2.2 (/lib64/libc.so.6+0x34950)
#15 0x0000000001071efa _start
(/root/dev/llvm-project/build/bin/llvm-exegesis+0x1071efa)
FileCheck error: '<stdin>' is empty.
FileCheck command line:  /root/dev/llvm-project/build/bin/FileCheck
/root/dev/llvm-project/llvm/test/tools/llvm-exegesis/X86/inverse_throughput/inverse_throughput-PBLENDVBrr0.s

  parent reply	other threads:[~2023-03-09 16:29 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-02 18:15 [Bug libgcc/108994] New: LLVM JIT segfaults in libgcc after upgrading from gcc 12.2.1 to 13.0.1 tstellar at redhat dot com
2023-03-02 18:19 ` [Bug libgcc/108994] [13 Regression] " redi at gcc dot gnu.org
2023-03-02 19:15 ` pinskia at gcc dot gnu.org
2023-03-02 19:19 ` tstellar at redhat dot com
2023-03-02 20:09 ` pinskia at gcc dot gnu.org
2023-03-03  3:13 ` tstellar at redhat dot com
2023-03-03  3:29 ` pinskia at gcc dot gnu.org
2023-03-03  7:39 ` tstellar at redhat dot com
2023-03-03  7:45 ` pinskia at gcc dot gnu.org
2023-03-03  7:46 ` pinskia at gcc dot gnu.org
2023-03-03  7:47 ` redi at gcc dot gnu.org
2023-03-03  8:45 ` [Bug target/108994] " jakub at gcc dot gnu.org
2023-03-03 18:37 ` tstellar at redhat dot com
2023-03-04  0:15 ` tstellar at redhat dot com
2023-03-06 12:37 ` [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 marxin at gcc dot gnu.org
2023-03-09 16:29 ` tstellar at redhat dot com [this message]
2023-03-09 18:50 ` tstellar at redhat dot com
2023-03-10 17:18 ` jakub at gcc dot gnu.org
2023-03-10 17:37 ` tstellar at redhat dot com
2023-03-14  5:41 ` tstellar at redhat dot com
2023-03-14  7:04 ` jakub at gcc dot gnu.org
2023-03-14 17:22 ` tstellar at redhat dot com
2023-03-14 18:08 ` pinskia at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-108994-4-vI4s7yBTwh@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).