public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/97102] [nvptx] PTX JIT compilation failed when using aliases
Date: Tue, 22 Sep 2020 06:10:04 +0000 [thread overview]
Message-ID: <bug-97102-4-vdVCOuxTXb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97102-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97102
--- Comment #4 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tobias Burnus from comment #2)
> Created attachment 49239 [details]
> Draft patch
>
> PTX ISA Notes
> .alias directive introduced in PTX ISA 6.3.
>
> Thus, it does not work everywhere :-(
>
> Patch – I did bump '.version' - but that probably has more side effects than
> desirable.
This patch does manage to complete a build, but tests (both standalone and
libgomp) using alias fail with "unresolved symbol". This is because it calls
write_fn_proto which generates a linker marker for the alias, which makes the
linker think there's such a function, and when it cannot find it, it generates
an "unresolved symbol" error.
next prev parent reply other threads:[~2020-09-22 6:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 7:15 [Bug target/97102] New: " burnus at gcc dot gnu.org
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 [this message]
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-vdVCOuxTXb@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).