public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/97102] New: [nvptx] PTX JIT compilation failed when using aliases Date: Fri, 18 Sep 2020 07:15:25 +0000 [thread overview] Message-ID: <bug-97102-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97102 Bug ID: 97102 Summary: [nvptx] PTX JIT compilation failed when using aliases Product: gcc Version: 11.0 Status: UNCONFIRMED Keywords: openmp Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: burnus at gcc dot gnu.org CC: vries at gcc dot gnu.org Target Milestone: --- [Found when testing a patch for PR96390, which works with GCN offloading but not with nvptx] When compiling the following with -fopenmp -------------------------------------- #pragma omp declare target int foo () { return 42; } int bar () __attribute__((alias ("foo"))); #pragma omp end declare target int main () { int n; #pragma omp target map(from:n) n = bar (); if (n != 42) __builtin_abort (); } -------------------------------------- it fails with when running with: libgomp: Link error log ptxas application ptx input, line 89; error : Label expected for argument 0 of instruction 'call' ptxas application ptx input, line 89; fatal : Call target not recognized ptxas fatal : Ptx assembly aborted due to errors libgomp: cuLinkAddData (ptx_code) error: a PTX JIT compilation failed The generated PTX has: ------------ // BEGIN GLOBAL FUNCTION DECL: foo .visible .func (.param.u32 %value_out) foo; // BEGIN GLOBAL FUNCTION DEF: foo .visible .func (.param.u32 %value_out) foo { .reg.u32 %value; .reg.u32 %r22; .reg.u32 %r23; mov.u32 %r22, 42; mov.u32 %r23, %r22; mov.u32 %value, %r23; st.param.u32 [%value_out], %value; ret; } ... call (%value_in), bar; ------ Namely: 'bar' only appears in the call.
next reply other threads:[~2020-09-18 7:15 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-18 7:15 burnus at gcc dot gnu.org [this message] 2020-09-18 8:04 ` [Bug target/97102] " burnus at gcc dot gnu.org 2020-09-18 10:27 ` burnus at gcc dot gnu.org 2020-09-18 10:42 ` burnus at gcc dot gnu.org 2020-09-22 6:10 ` vries at gcc dot gnu.org 2020-09-22 7:18 ` vries at gcc dot gnu.org 2020-09-22 8:09 ` vries at gcc dot gnu.org 2020-09-23 7:25 ` vries at gcc dot gnu.org 2020-09-23 7:31 ` vries at gcc dot gnu.org 2021-05-12 16:39 ` vries at gcc dot gnu.org 2022-03-22 13:59 ` vries at gcc dot gnu.org 2022-09-07 8:02 ` 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-97102-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: 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).