public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: Nick Clifton <nickc@redhat.com>
Cc: Ramana Radhakrishnan <ramana.radhakrishnan@linaro.org>,
	richard.earnshaw@arm.com, gcc-patches@gcc.gnu.org
Subject: Re: RFC: ARM: Add comment enumerating emitted .eabi_attribute tags
Date: Tue, 27 Sep 2011 18:19:00 -0000	[thread overview]
Message-ID: <201109271833.28851.paul@codesourcery.com> (raw)
In-Reply-To: <4E81FE66.5000206@redhat.com>

>    2. Abandon using a header file at all.  Instead use a configure test
> to see if we are using an assembler that supports textual names in a
> .eabi_attribute directive and if so use the names rather than the numbers.

I'm not sure this is mutually exclusive with using a header file, but using 
the names where possible sounds like a nice idea in principle.

There are practical issues with tags introduced in newer EABI revisions (which 
may not be supported by older assemblers).  However you probably need linker 
support anyway and get the new assembler for free in that case.  I wouldn't 
put money on old binutils working reliably with new gcc in the first place.

Paul

  reply	other threads:[~2011-09-27 17:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-27 15:51 Nick Clifton
2011-09-27 16:47 ` Ramana Radhakrishnan
2011-09-27 16:58   ` Paul Brook
2011-09-27 17:01     ` Ramana Radhakrishnan
2011-09-27 17:17   ` Nick Clifton
2011-09-27 18:19     ` Paul Brook [this message]
2011-09-27 16:49 ` Richard Henderson
2011-09-27 17:23   ` Nick Clifton

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=201109271833.28851.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=nickc@redhat.com \
    --cc=ramana.radhakrishnan@linaro.org \
    --cc=richard.earnshaw@arm.com \
    /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).