public inbox for java-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@arm.com>
To: Matthias Klose <doko@ubuntu.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	 GCJ-patches <java-patches@gcc.gnu.org>,
	"libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>
Subject: Re: [patch] [gcc/libgcc/ada/libstdc++] Match arm*-*-linux-*eabi* for ARM Linux/GNU EABI
Date: Tue, 26 Jun 2012 09:10:00 -0000	[thread overview]
Message-ID: <4FE97C7F.8060308@arm.com> (raw)
In-Reply-To: <4FE8D88D.7040300@ubuntu.com>

On 25/06/12 22:30, Matthias Klose wrote:
> On 25.06.2012 18:21, Matthias Klose wrote:
>> On 25.06.2012 15:22, Richard Earnshaw wrote:
>>> On 25/06/12 13:08, Matthias Klose wrote:
>>>> gcc/config.gcc now allows matching arm*-*-linux-*eabi* instead of
>>>> arm*-*-linux-*eabi for ARM Linux/GNU EABI.  This changes the matching in various
>>>> other places as well. arm-linux-gnueabihf is used as a triplet by some
>>>> distributions.
>>>>
>>>> Ok for the trunk?
>>>>
>>>
>>> now that all arm-linux ports are EABI conforming, why can't this just become
>>>
>>> 	arm*-*-linux*
>>> ?
>>
>> I assume it could. But I didn't check for other places where this would be needed.
> 
> $ grep -r 'arm[^_]*eabi' . |egrep -v 'ChangeLog|\.svn/'|wc -l
> 87
> 
> this seems to be a larger change, which should have been committed when the old
> abi targets were deprecated.  I'd like to get the eabi* change in first.
> 
>   Matthias
> 
> 

Removal of the FPA support is still ongoing, but beware that it doesn't
mean that all supported ARM configurations will be EABI conforming (some
configurations did not use the FPA and are thus not affected by this
change); but all ARM Linux configurations will be.

R.



  reply	other threads:[~2012-06-26  9:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-25 12:10 Matthias Klose
2012-06-25 13:23 ` Richard Earnshaw
2012-06-25 16:22   ` Matthias Klose
2012-06-25 21:32     ` Matthias Klose
2012-06-26  9:10       ` Richard Earnshaw [this message]
2012-10-15 14:25         ` Matthias Klose
2012-10-15 15:42           ` Richard Earnshaw

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=4FE97C7F.8060308@arm.com \
    --to=rearnsha@arm.com \
    --cc=doko@ubuntu.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=java-patches@gcc.gnu.org \
    --cc=libstdc++@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).