From: Richard Sandiford <rdsandiford@googlemail.com>
To: Andrew Bennett <Andrew.Bennett@imgtec.com>
Cc: "gcc-patches\@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Matthew Fortune <Matthew.Fortune@imgtec.com>,
Saeed Ghazanfar <Saeed.Ghazanfar@imgtec.com>,
Rich Fuhler <Rich.Fuhler@imgtec.com>
Subject: Re: [PATCH] Add support for MIPS r3 and r5
Date: Fri, 09 May 2014 11:07:00 -0000 [thread overview]
Message-ID: <87a9arjjmv.fsf@sandifor-thinkpad.stglab.manchester.uk.ibm.com> (raw)
In-Reply-To: <0DA23CC379F5F945ACB41CF394B982775792ED@LEMAIL01.le.imgtec.org> (Andrew Bennett's message of "Fri, 9 May 2014 10:40:02 +0000")
Andrew Bennett <Andrew.Bennett@imgtec.com> writes:
>> > @@ -141,7 +151,8 @@ along with GCC; see the file COPYING3. If not see
>> > "%{EL:-m elf32lmip} \
>> > %{EB:-m elf32bmip} \
>> > %(endian_spec) \
>> > - %{G*} %{mips1} %{mips2} %{mips3} %{mips4} %{mips32} %{mips32r2}
>> %{mips64} \
>> > + %{G*} %{mips1} %{mips2} %{mips3} %{mips4} %{mips32} %{mips32r2}
>> \
>> > + %{mips32r3} %{mips32r5} %{mips64} \
>> > %(netbsd_link_spec)"
>> >
>> > #define NETBSD_ENTRY_POINT "__start"
>>
>> Not sure the omission of mips64r2 was deliberate here, or in vxworks.h.
>
> Yes it was deliberate: mips64r2 was already missing from the original ASM_SPEC
> in vxworks.h and the LINK_SPEC in netbsfd.h.
Right, but that's what I was saying didn't look deliberate. I expect
it was just missed when mips64r2 was added.
Thanks,
Richard
next prev parent reply other threads:[~2014-05-09 11:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-08 13:47 Andrew Bennett
2014-05-08 17:23 ` Joseph S. Myers
2014-05-08 19:27 ` Richard Sandiford
2014-05-09 10:40 ` Andrew Bennett
2014-05-09 11:07 ` Richard Sandiford [this message]
2014-05-09 11:26 ` Andrew Bennett
2014-05-10 9:16 ` Richard Sandiford
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=87a9arjjmv.fsf@sandifor-thinkpad.stglab.manchester.uk.ibm.com \
--to=rdsandiford@googlemail.com \
--cc=Andrew.Bennett@imgtec.com \
--cc=Matthew.Fortune@imgtec.com \
--cc=Rich.Fuhler@imgtec.com \
--cc=Saeed.Ghazanfar@imgtec.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).