public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/105018] [nvptx] Need better alias support
Date: Fri, 22 Jul 2022 13:02:57 +0000 [thread overview]
Message-ID: <bug-105018-4-TCqukMoZE3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105018-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105018
Thomas Schwinge <tschwinge at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://github.com/MentorEm
| |bedded/nvptx-tools/issues/3
| |2
Last reconfirmed| |2022-07-22
CC| |amonakov at gcc dot gnu.org,
| |tschwinge at gcc dot gnu.org
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
--- Comment #3 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #2)
> As mentioned before by amonakov, a possibility is to add alias support to
> the nvptx-tools linker, and use that.
<https://github.com/MentorEmbedded/nvptx-tools/issues/32> "[LD] Handle alias in
nvptx-ld as nvptx's .alias does not handle it fully".
Alexander, you don't happen to have started working on this already?
prev parent reply other threads:[~2022-07-22 13:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 14:29 [Bug target/105018] New: " vries at gcc dot gnu.org
2022-03-22 14:30 ` [Bug target/105018] " vries at gcc dot gnu.org
2022-03-22 14:34 ` vries at gcc dot gnu.org
2022-07-22 13:02 ` tschwinge at gcc dot gnu.org [this message]
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-105018-4-TCqukMoZE3@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).