public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgcc/110955] SIGSEGV in libgcc_s.so.1`classify_object_over_fdes+0x140 on Solaris SPARC with GCC 13 runtime Date: Fri, 11 Aug 2023 08:12:38 +0000 [thread overview] Message-ID: <bug-110955-4-ELgLrAABP2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110955-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110955 --- Comment #14 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> --- > --- Comment #13 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot > Uni-Bielefeld.DE> --- >> --- Comment #12 from Petr Sumbera <sumbera at volny dot cz> --- >> (In reply to Petr Sumbera from comment #9) >>> (In reply to ro@CeBiTec.Uni-Bielefeld.DE from comment #8) >>> > > without the JIT patch (033-solaris-LLVM-JIT.patch)? It may be worth a try >>> > > until someone fixes and integrates SPARC JIT support for real. >>> >>> I will try to build LLVM without the patch and will see. But the patch says >>> it >>> was created because of gnome-shell. >> >> When I updated test system with LLVM built without 033-solaris-LLVM-JIT.patch >> (without rebuilding any other component) it fails in different way (probably >> earlier). See bellow. I think that the patch is really needed. > [...] >> libLLVM-13.so`_ZN4llvm14RuntimeDyldELF23resolveX86_64RelocationERKNS_12SectionEntryEmmjlm+0x64(969a060b00?, >> 9699f673c0?, 20?, 7af3bfb12000?, 18?, 0?) > > Seems so. Calling llvm::RuntimeDyldELF::resolveX86_64Relocation on a > SPARC ELF file is obviously complete bullshit. Might be something > already fixed in newer LLVM versions. Somehow, the architecture > detection is amiss... That's almost certainly due to Solaris still including LLVM 13, which is pretty old by now. In particular, it lacks llvm::sys::getHostCPUName. My patch to implement this on SPARC only landed in LLVM 16. > However, given my impression from the mesa code is that even a proper > error handling in RuntimeDyLD wouldn't help there. Mesa uses the same function, so this may well be a second instance of the same problem.
next prev parent reply other threads:[~2023-08-11 8:12 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-09 6:57 [Bug libgcc/110955] New: " sumbera at volny dot cz 2023-08-09 7:13 ` [Bug libgcc/110955] " pinskia at gcc dot gnu.org 2023-08-09 7:19 ` pinskia at gcc dot gnu.org 2023-08-09 7:47 ` schwab@linux-m68k.org 2023-08-09 10:00 ` sumbera at volny dot cz 2023-08-09 11:33 ` tneumann at users dot sourceforge.net 2023-08-09 11:34 ` ro at gcc dot gnu.org 2023-08-09 11:53 ` ro at gcc dot gnu.org 2023-08-10 8:55 ` ro at gcc dot gnu.org 2023-08-10 10:47 ` ro at CeBiTec dot Uni-Bielefeld.DE 2023-08-10 11:20 ` sumbera at volny dot cz 2023-08-10 11:22 ` ro at CeBiTec dot Uni-Bielefeld.DE 2023-08-10 13:52 ` ro at CeBiTec dot Uni-Bielefeld.DE 2023-08-10 13:56 ` sumbera at volny dot cz 2023-08-10 14:12 ` ro at CeBiTec dot Uni-Bielefeld.DE 2023-08-11 8:12 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message] 2023-08-11 8:22 ` ro at CeBiTec dot Uni-Bielefeld.DE 2023-08-11 13:34 ` sumbera at volny dot cz
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-110955-4-ELgLrAABP2@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: linkBe 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).