From: Richard Earnshaw <rearnsha@arm.com>
To: gcc@gcc.gnu.org
Cc: Kazu Hirata <kazu@codesourcery.com>,
rth@redhat.com, davem@redhat.com, jakub@redhat.com,
ebotcazou@libertysurf.fr
Subject: Re: Preparing to merge ARM/hard_vfp_branch to trunk
Date: Thu, 06 Aug 2009 19:35:00 -0000 [thread overview]
Message-ID: <1249569105.7024.2.camel@e200601-lin.cambridge.arm.com> (raw)
In-Reply-To: <1249478458.17762.33.camel@e200601-lin.cambridge.arm.com>
On Wed, 2009-08-05 at 14:20 +0100, Richard Earnshaw wrote:
> I think we are now in the position where we can merge the arm hard-vfp
> ABI code into trunk. There are no known issues with the compiler code
> and just one outstanding issue relating to tests and dealing with
> compiler variants (multilibs and other options). That issue shouldn't
> prevent merging.
>
> All the patches to non-arm code bar one have already received approval
> for mainline integration. The outstanding issue is a change to the
> SPARC back-end to account for a change to the LIBCALL_VALUE macro.
>
> I believe that I could legitimately approve that patch myself (it's
> pretty trivial and I didn't author it), but I'd prefer to get approval
> from one of the SPARC maintainers. Here's your chance:
>
> http://gcc.gnu.org/ml/gcc-patches/2009-04/msg01027.html
>
> Once that issue is taken care of, I don't think there are any further
> obstacles to completing the merge and propose to do that sometime over
> the next week.
>
> Comments/objections please?
>
> R.
I've now completed the merge. A couple of late issues that Joseph has
just reminded me of will now be fixed on the trunk.
R.
prev parent reply other threads:[~2009-08-06 14:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-05 15:28 Richard Earnshaw
2009-08-05 16:47 ` Eric Botcazou
2009-08-05 21:15 ` David Miller
2009-08-06 14:21 ` Joseph S. Myers
2009-08-06 19:35 ` Richard Earnshaw [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=1249569105.7024.2.camel@e200601-lin.cambridge.arm.com \
--to=rearnsha@arm.com \
--cc=davem@redhat.com \
--cc=ebotcazou@libertysurf.fr \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=kazu@codesourcery.com \
--cc=rth@redhat.com \
/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).