From: Mark Mitchell <mark@codesourcery.com>
To: Carlos O'Donell <carlos@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Pass more options to the assembler.
Date: Mon, 06 Aug 2007 03:16:00 -0000 [thread overview]
Message-ID: <46B6927D.1080002@codesourcery.com> (raw)
In-Reply-To: <20070801175134.GR18317@lios>
Carlos O'Donell wrote:
> The driver should pass -w, -I and -v to the gnu assembler.
>
> If the user requests -w (no warnings), then -W (no warnings) should be
> passed to the assembler. The passing of -I options to the assembler
> would allow .include and #include to share directories. Lastly, if the
> compiler is being verbose, the assembler should list a version string,
> so pass -v to the assembler aswell.
>
> Tested on arm-none-eabi, and i686-pc-linux-gnu without regressions.
>
> OK for mainline?
OK.
(It would have been helpful to other readers if you had noted that this
is only done when the assembler is GAS; obviously, for other assemblers,
you cannot make the same kinds of assumptions about flags.)
Thanks,
--
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713
prev parent reply other threads:[~2007-08-06 3:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 17:51 Carlos O'Donell
2007-08-06 3:16 ` Mark Mitchell [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=46B6927D.1080002@codesourcery.com \
--to=mark@codesourcery.com \
--cc=carlos@codesourcery.com \
--cc=gcc-patches@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).