From: Richard Sandiford <rdsandiford@googlemail.com>
To: "Steve Ellcey " <sellcey@mips.com>
Cc: <gcc-patches@gcc.gnu.org>
Subject: Re: [patch, mips] Change -mad to -mmad to match documentation
Date: Mon, 07 Jan 2013 20:33:00 -0000 [thread overview]
Message-ID: <87ehhw4ttn.fsf@talisman.default> (raw)
In-Reply-To: <786b4481-9093-40bc-ae04-d3501a4a05ef@EXCHHUB01.MIPS.com> (Steve Ellcey's message of "Mon, 7 Jan 2013 11:27:26 -0800")
"Steve Ellcey " <sellcey@mips.com> writes:
> The MIPS documentation describes a -mmad (-mno-mad) flag, but it is incorrectly
> implemented as -mad (-mno-ad) instead. This patch changes the implementation
> to match the documentation. This means that users who are currently using the
> -mad or -mno-ad flags would have to change. If we want we could leave -mad and
> -mno-ad as aliases for -mmad and -mno-ad but I don't think that is necessary.
>
> If someone does think we should do allow -mad, please let me know.
>
> OK to checkin?
OK, thanks. Looks like I introduced this in the TARGET_OPTINS ->
.opt-file conversion.
Richard
prev parent reply other threads:[~2013-01-07 20:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 19:27 Steve Ellcey
2013-01-07 20:33 ` Richard Sandiford [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=87ehhw4ttn.fsf@talisman.default \
--to=rdsandiford@googlemail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=sellcey@mips.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).