From: "Cristian Rodríguez" <cristian@rodriguez.im>
To: Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>
Subject: rustc SIGILL since qsort_r patches
Date: Sat, 4 Nov 2023 21:55:06 -0300 [thread overview]
Message-ID: <CAPBLoAfg-S2s6GMsFqMghOwpzjNe5SbLh_6_uDEmZ8Wg4ztcVA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1052 bytes --]
Hi:
After quite some head scratching I found the recent qsort_r patches
triggers a bug "somewhere" that makes rustc LTO end in sigkill (ud2)
happens compiling anything in release mode with any toolchain (stable,
beta, nightly)
#0 0x000015129e40516a in int
llvm::array_pod_sort_comparator<llvm::BranchFolder::MergePotentialsElt>(void
const*, void const*) () from
/home/crrodriguez/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/bin/../lib/../lib/
libLLVM-17-rust-1.75.0-nightly.so
#1 0x00001512a0043779 in __GI___qsort_r (pbase=0x15128c90bd80,
total_elems=<optimized out>, size=0x10, cmp=<optimized out>, arg=<optimized
out>) at qsort.c:335
#2 0x000015129e4df6e6 in
llvm::BranchFolder::TryTailMergeBlocks(llvm::MachineBasicBlock*,
llvm::MachineBasicBlock*, unsigned int) () from
/home/crrodriguez/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/bin/../lib/../lib/
libLLVM-17-rust-1.75.0-nightly.so
git head == bad
2.38 == good
Main interest is to know if I am not alone and if anyone else has observed
this problem so far.
Thanks..
next reply other threads:[~2023-11-05 0:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-05 0:55 Cristian Rodríguez [this message]
2023-11-05 1:10 ` Andrew Pinski
2023-11-05 1:13 ` Andrew Pinski
2023-11-05 12:15 ` Cristian Rodríguez
2023-11-06 14:13 ` Adhemerval Zanella Netto
2023-11-07 11:09 ` Florian Weimer
2023-11-07 12:48 ` Adhemerval Zanella Netto
2023-11-07 13:04 ` Florian Weimer
2023-11-07 13:07 ` Adhemerval Zanella Netto
2023-11-07 13:13 ` Florian Weimer
2023-11-07 13:26 ` Adhemerval Zanella Netto
2023-11-07 14:02 ` Florian Weimer
2023-11-07 14:57 ` Stepan Golosunov
2023-11-07 16:05 ` Florian Weimer
2023-11-17 10:35 ` Florian Weimer
2023-11-17 11:44 ` Adhemerval Zanella Netto
2023-11-17 13:33 ` Florian Weimer
2023-11-17 13:57 ` Florian Weimer
2023-11-17 16:17 ` Florian Weimer
2023-11-17 18:37 ` Adhemerval Zanella
2023-11-07 14:32 ` Florian Weimer
2023-11-08 14:19 ` Florian Weimer
2023-11-08 19:56 ` Cristian Rodríguez
2023-11-09 11:49 ` Cristian Rodríguez
2023-11-09 12:40 ` Adhemerval Zanella Netto
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=CAPBLoAfg-S2s6GMsFqMghOwpzjNe5SbLh_6_uDEmZ8Wg4ztcVA@mail.gmail.com \
--to=cristian@rodriguez.im \
--cc=libc-alpha@sourceware.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).