From: Nick Clifton <nickc@redhat.com>
To: Richard Henderson <rth@redhat.com>
Cc: richard.earnshaw@arm.com, paul@codesourcery.com,
ramana.radhakrishnan@arm.com, gcc-patches@gcc.gnu.org
Subject: Re: RFC: ARM: Add comment enumerating emitted .eabi_attribute tags
Date: Tue, 27 Sep 2011 17:23:00 -0000 [thread overview]
Message-ID: <4E81FEE6.7080504@redhat.com> (raw)
In-Reply-To: <4E81ED63.2090404@redhat.com>
Hi Richard,
> You should only emit the comment for -dA, I think.
Really ? I thought that it was kind of nice to have the comments in the
default output.
If I go with -dA as the trigger then I assume that it is also OK to add
the comments if --verbose-asm is enabled, yes ?
Cheers
Nick
prev parent reply other threads:[~2011-09-27 16:49 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
2011-09-27 16:49 ` Richard Henderson
2011-09-27 17:23 ` Nick Clifton [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=4E81FEE6.7080504@redhat.com \
--to=nickc@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=paul@codesourcery.com \
--cc=ramana.radhakrishnan@arm.com \
--cc=richard.earnshaw@arm.com \
--cc=rth@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).