From: Richard Sandiford <richard@codesourcery.com>
To: Thiemo Seufer <ths@networkno.de>
Cc: binutils@sourceware.org
Subject: Re: [PATCH] Better checking of ISA/ASE/ABI options for MIPS gas
Date: Wed, 24 May 2006 01:46:00 -0000 [thread overview]
Message-ID: <87y7wsagj2.fsf@talisman.home> (raw)
In-Reply-To: <20060523153720.GF9061@networkno.de> (Thiemo Seufer's message of "Tue, 23 May 2006 16:37:20 +0100")
Thiemo Seufer <ths@networkno.de> writes:
> Richard Sandiford wrote:
> [snip]
>> > Richard, do you care about the gcc update (if/when the release cycle
>> > permits it)?
>>
>> I'm not sure what you mean here, but I'd certainly like to see gcc's &
>> gas's option handling kept in sync, so the gcc equivalent of this patch
>> is certainly welcome from my POV. And I'd see a long-lasting divergence
>> between gas and gcc as a bug, so I'd be happy to use the discretion
>> given to target maintainers and have the patch go in during stage 3.
>
> Well, the divergence is caused by missing MIPS32R2 with 64bit FP support
> on the gcc side, which is a too invasive change for stage 3. IOW, the
> re-sync of the option handling will be included in that patch, hopefully
> in time for next stage 1.
OK, that's fine too ;)
Richard
prev parent reply other threads:[~2006-05-23 15:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-23 0:08 Thiemo Seufer
2006-05-23 4:06 ` Eric Christopher
2006-05-23 4:40 ` Thiemo Seufer
2006-05-23 5:01 ` Eric Christopher
2006-05-23 5:27 ` Thiemo Seufer
2006-05-23 5:51 ` Eric Christopher
2006-05-23 12:10 ` Richard Sandiford
2006-05-23 13:34 ` Thiemo Seufer
2006-05-23 14:14 ` Richard Sandiford
2006-05-23 15:39 ` Thiemo Seufer
2006-05-23 17:47 ` Thiemo Seufer
2006-05-23 21:01 ` Richard Sandiford
2006-05-23 23:37 ` Thiemo Seufer
2006-05-24 1:46 ` 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=87y7wsagj2.fsf@talisman.home \
--to=richard@codesourcery.com \
--cc=binutils@sourceware.org \
--cc=ths@networkno.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).