public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/94278] [amdgcn] Offloading build failures due to 'llvm-mc' SIGSEGV Date: Wed, 21 Apr 2021 12:27:59 +0000 [thread overview] Message-ID: <bug-94278-4-QCtYrkR1nP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94278-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94278 --- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> --- I'm running into the same issue (and filed PR100181) but with llvm11 based llvm-mc the CUs are instead rejected due to a section crossing jump: ./pr93515.xamdgcn-amdhsa.mkoffload.2.s:634:2: error: undefined label '.L33' s_branch .L33 ^ mkoffload: fatal error: /usr/bin//x86_64-suse-linux-accel-amdgcn-amdhsa-gcc-11 returned 1 exit status s_branch .L33 .section .text.unlikely .type main._omp_fn.4.cold, @function main._omp_fn.4.cold: .L33: s_getpc_b64 s[2:3] s_add_u32 s2, s2, abort@rel32@lo+4 s_addc_u32 s3, s3, abort@rel32@hi+4 s_swappc_b64 s[18:19], s[2:3] .text
next prev parent reply other threads:[~2021-04-21 12:28 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-23 13:45 [Bug target/94278] New: " tschwinge at gcc dot gnu.org 2020-04-21 13:02 ` [Bug target/94278] " tschwinge at gcc dot gnu.org 2020-04-21 13:23 ` ams at gcc dot gnu.org 2020-04-22 10:13 ` tschwinge at gcc dot gnu.org 2020-04-23 12:45 ` ams at gcc dot gnu.org 2021-04-21 12:27 ` rguenth at gcc dot gnu.org [this message] 2021-04-21 12:32 ` rguenth at gcc dot gnu.org 2021-04-21 13:09 ` rguenth at gcc dot gnu.org 2021-04-21 13:59 ` rguenth at gcc dot gnu.org 2021-07-19 16:00 ` burnus 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-94278-4-QCtYrkR1nP@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).