From: Nick Clifton <nickc@redhat.com>
To: morrell@alumni.ucsd.edu, binutils@sourceware.org
Subject: Re: Commit: Gas: Add .nop directive.
Date: Mon, 14 Sep 2020 17:31:36 +0100 [thread overview]
Message-ID: <7a474cb0-829e-8493-d49c-b9a5bc1c5440@redhat.com> (raw)
In-Reply-To: <1396691708.4116097.1600099454135@mail.yahoo.com>
Hi Michael,
> Once this is in, I hope this code from gcc/configure can be removed:
That would be a nice thing to do, but I am not sure that it will work. Since
gcc still needs to remain compatible with older versions of the binutils I
think that code will need to remain.
What could happen though is that the test could be taught about the new directive
and if it is supported, use it. This would mean that future new architectures
would not have to have any code added here, the test should just work.
I am contemplating backporting the patch to the 2.35 branch and then triggering
a 2.35.1 point release. (Actually there are a few more DWARF-5 patches that need
to go in, and then it might be a good time for a point release). So in theory
the test in gcc could check for binutils 2.35.1 or later, and if present, just
use the .nop directive, without having to worry about anything target specific.
Cheers
Nick
next prev parent reply other threads:[~2020-09-14 16:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.151032.1600097231.8982.binutils@sourceware.org>
2020-09-14 16:04 ` Michael Morrell
2020-09-14 16:31 ` Nick Clifton [this message]
2020-09-15 3:52 ` 2.35.1 (was: Commit: Gas: Add .nop directive.) Hans-Peter Nilsson
2020-09-15 10:31 ` Nick Clifton
2020-09-15 11:47 ` Hans-Peter Nilsson
2020-09-15 12:45 ` Nick Clifton
2020-09-15 9:53 ` Commit: Gas: Add .nop directive Nick Clifton
2020-09-14 15:13 Nick Clifton
2020-09-14 15:27 ` Jose E. Marchesi
2020-09-15 11:13 ` Nick Clifton
2020-09-15 11:57 ` Jose E. Marchesi
2020-09-14 15:38 ` Andreas Schwab
2020-09-14 16:02 ` Nick Clifton
2020-09-30 18:18 ` Maciej W. Rozycki
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=7a474cb0-829e-8493-d49c-b9a5bc1c5440@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=morrell@alumni.ucsd.edu \
/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).