From: Mike Frysinger <vapier@gentoo.org>
To: Michael Hope <michael.hope@linaro.org>
Cc: libc-ports@sourceware.org, cross-distro@lists.linaro.org,
Richard Guenther <rguenther@suse.de>,
Richard Earnshaw <rearnsha@arm.com>,
"Carlos O'Donell" <carlos@systemhalted.org>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Andreas Jaeger <aj@suse.com>
Subject: Re: [PATCH v2] ARM: Use different linker path for hardfloat ABI
Date: Thu, 24 May 2012 04:08:00 -0000 [thread overview]
Message-ID: <201205240009.49015.vapier@gentoo.org> (raw)
In-Reply-To: <CANLjY-=unqAnKAa6jpyvYo1N8-xEQJM0DMXKi8i2NUfxjMG-vw@mail.gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 1668 bytes --]
On Wednesday 23 May 2012 17:11:53 Michael Hope wrote:
> On 24 May 2012 02:16, Mike Frysinger wrote:
> > On Wednesday 23 May 2012 04:17:51 Richard Guenther wrote:
> >> On Wed, 23 May 2012, Andreas Jaeger wrote:
> >> > On Wednesday, May 23, 2012 09:56:31 Richard Earnshaw wrote:
> >> > > [...]
> >> > > This is a behaviour change. It would need RM approval for a release
> >> > > branch.
> >> > >
> >> > > R.
> >> >
> >> > There was agreement by all pushing for the change to use it. So, let's
> >> > ask the release managers about their opinion,
> >>
> >> I'm ok with the change - but of course only to carry one less patch
> >> in our local tree. What do others think? It would definitely (anyway)
> >> need documenting in changes.html (for both 4.7.1 and 4.8).
> >
> > i've done this for Gentoo and 4.5.0+, so if all the distros are going to
> > be doing this in 4.7.x anyways, makes sense to me to do it in the
> > official branch.
>
> Agreed. Google have done it for their 4.6, Fedora have done it for
> 4.7 (?), and we've done it for Linaro GCC 4.6 and 4.7.
>
> My concern is that a point release of GCC would stop working against
> the latest release of GLIBC.
>
> I'm happy to prepare a backport to GCC 4.6, GCC 4.7, and GLIBC 2.15 so
> the next set of point releases will all work with each other. This
> would match what the distros are doing.
http://sources.gentoo.org/gentoo/src/patchsets/gcc/4.6.3/gentoo/33_all_armhf.patch
http://sources.gentoo.org/gentoo/src/patchsets/gcc/4.7.0/gentoo/33_all_armhf.patch
http://sources.gentoo.org/gentoo/src/patchsets/glibc/2.15/6226_all_arm-glibc-2.15-hardfp.patch
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-05-24 4:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-22 22:20 Michael Hope
2012-04-23 15:37 ` Richard Earnshaw
2012-04-23 21:37 ` Michael Hope
2012-04-24 13:32 ` Richard Earnshaw
2012-04-26 20:21 ` Carlos O'Donell
2012-04-26 23:27 ` Michael Hope
2012-04-30 15:24 ` Richard Earnshaw
2012-04-30 21:48 ` Michael Hope
2012-04-30 22:01 ` Jeff Law
2012-05-01 2:44 ` Michael Hope
2012-05-01 3:46 ` Jeff Law
2012-05-01 8:52 ` Richard Earnshaw
2012-05-23 7:13 ` Andreas Jaeger
2012-05-23 7:56 ` Richard Earnshaw
2012-05-23 8:01 ` Andreas Jaeger
2012-05-23 8:18 ` Richard Guenther
2012-05-23 14:15 ` Mike Frysinger
2012-05-23 21:12 ` Michael Hope
2012-05-24 4:08 ` Mike Frysinger [this message]
2012-05-24 8:15 ` Andrew Haley
2012-05-25 0:27 ` Mike Frysinger
2012-05-25 8:24 ` Andrew Haley
2012-05-24 17:08 ` Jakub Jelinek
2012-04-23 19:58 ` Carlos O'Donell
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=201205240009.49015.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=aj@suse.com \
--cc=carlos@systemhalted.org \
--cc=cross-distro@lists.linaro.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=libc-ports@sourceware.org \
--cc=michael.hope@linaro.org \
--cc=rearnsha@arm.com \
--cc=rguenther@suse.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).