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/100181] New: hot-cold partitioned code doesn't assemble
Date: Wed, 21 Apr 2021 12:19:33 +0000 [thread overview]
Message-ID: <bug-100181-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100181
Bug ID: 100181
Summary: hot-cold partitioned code doesn't assemble
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: rguenth at gcc dot gnu.org
Target Milestone: ---
I see lots of libgomp fails with offloading for amdgcn like
./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
which is because we compile to
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
and thus have a section crossing jump using a local label. The amdgcn
assembler
I'm using doesn't like this, it is
> amdgcn-amdhsa-as --version
LLVM (http://llvm.org/):
LLVM version 11.0.1
Optimized build.
Default target: x86_64-unknown-linux-gnu
Host CPU: znver2
next reply other threads:[~2021-04-21 12:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 12:19 rguenth at gcc dot gnu.org [this message]
2021-04-21 12:22 ` [Bug target/100181] " rguenth at gcc dot gnu.org
2021-04-21 12:23 ` rguenth at gcc dot gnu.org
2021-04-21 12:25 ` rguenth at gcc dot gnu.org
2021-04-21 12:26 ` rguenth at gcc dot gnu.org
2021-04-21 12:27 ` tschwinge at gcc dot gnu.org
2021-04-21 12:32 ` rguenth at gcc dot gnu.org
2021-04-21 12:43 ` burnus at gcc dot gnu.org
2021-04-21 12:52 ` tschwinge at gcc dot gnu.org
2021-04-21 14:42 ` burnus at gcc dot gnu.org
2021-07-19 15:59 ` burnus at gcc dot gnu.org
2021-07-19 16:00 ` burnus at gcc dot gnu.org
2022-02-11 14:08 ` burnus at gcc dot gnu.org
2022-02-11 14:27 ` ams at gcc dot gnu.org
2022-05-27 19:44 ` tschwinge 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-100181-4@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).