From: "Richard Earnshaw (home)" <richard.earnshaw@buzzard.freeserve.co.uk>
To: Nick Clifton <nickc@redhat.com>
Cc: "binutils@sourceware.org" <binutils@sourceware.org>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
"aph@redhat.com" <aph@redhat.com>
Subject: Re: RFC: Collecting together binary file attributes into a single file.
Date: Thu, 29 Sep 2011 10:12:00 -0000 [thread overview]
Message-ID: <7466E409-8C17-408C-82C6-E0A1C6AD3D20@buzzard.freeserve.co.uk> (raw)
In-Reply-To: <m3mxdnbsju.fsf@redhat.com>
On 29 Sep 2011, at 10:34, "Nick Clifton" <nickc@redhat.com> wrote:
> Hi Guys,
>
> All I wanted to do was to make GCC's ARM assembler output slightly
> easier to read...
>
> I would like to propose a patch to create a new header file in the
> include/ directory. This file would contain enums describing the
> attributes that be can found in SHT_GNU_ATTRIBUTES sections. The
> purpose of the file is to provide a single place where these values
> are defined, and to share the information between GCC, BINUTILS and
> GDB.
>
> The patch also includes an update to readelf to make it use the
> enumerated values and an example of a patch to the ARM backend of GCC
> to include the attribute names in its assembler output.
>
>
> So - what do people think ? Any objections to this idea ?
>
I don't think it's a good idea to have the attributes of every CPU we support in a single file. That's going to get unmaintainable very quickly.
R
next prev parent reply other threads:[~2011-09-29 9:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 9:38 Nick Clifton
2011-09-29 10:12 ` Richard Earnshaw (home) [this message]
2011-09-29 14:14 ` Nick Clifton
2011-09-29 17:57 ` Joseph S. Myers
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=7466E409-8C17-408C-82C6-E0A1C6AD3D20@buzzard.freeserve.co.uk \
--to=richard.earnshaw@buzzard.freeserve.co.uk \
--cc=aph@redhat.com \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=nickc@redhat.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