From: "Moore, Catherine" <Catherine_Moore@mentor.com>
To: Matthew Fortune <Matthew.Fortune@imgtec.com>
Cc: "'gcc-patches@gcc.gnu.org' (gcc-patches@gcc.gnu.org)"
<gcc-patches@gcc.gnu.org>,
"roland.illig@gmx.de" <roland.illig@gmx.de>
Subject: RE: [patch, MIPS] Update -mvirt option description
Date: Thu, 06 Apr 2017 15:23:00 -0000 [thread overview]
Message-ID: <6aacf6e685b54762825d964b5ef611fb@svr-orw-mbx-03.mgc.mentorg.com> (raw)
In-Reply-To: <6D39441BF12EF246A7ABCE6654B0235380BE22A2@HHMAIL01.hh.imgtec.org>
> -----Original Message-----
> From: Matthew Fortune [mailto:Matthew.Fortune@imgtec.com]
> Sent: Friday, March 31, 2017 4:00 PM
> To: Moore, Catherine <Catherine_Moore@mentor.com>
> Cc: 'gcc-patches@gcc.gnu.org' (gcc-patches@gcc.gnu.org) <gcc-
> patches@gcc.gnu.org>; roland.illig@gmx.de
> Subject: [patch, MIPS] Update -mvirt option description
>
> Hi Catherine,
>
> I'm following up on PR target/80057 to update the description of -
> mvirt.
>
> I agree with Roland that the description is inconsistent and should not
> state 'application specific' as none of the other ASE options include
> it. Instead I suggest we put the shortened form of (VZ) in like (XPA)
> is shown for -mxpa. The short form of virtualization ASE is usually VZ
> not VIRT which has always irritated me about this option name but
> that
> is history.
>
> What do you think?
This looks good to me.
>
> gcc/
> PR target/80057
> * config/mips/mips.opt (-mvirt): Update description.
>
prev parent reply other threads:[~2017-04-06 15:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-31 20:25 Matthew Fortune
2017-04-06 15:23 ` Moore, Catherine [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=6aacf6e685b54762825d964b5ef611fb@svr-orw-mbx-03.mgc.mentorg.com \
--to=catherine_moore@mentor.com \
--cc=Matthew.Fortune@imgtec.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=roland.illig@gmx.de \
/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).