From: Marcus Shawcroft <marcus.shawcroft@gmail.com>
To: James Greenhalgh <james.greenhalgh@arm.com>
Cc: gcc-patches@gcc.gnu.org, apinski@cavium.com, marcus.shawcroft@arm.com
Subject: Re: [AArch64-4.7] Backport: Fix g++.dg/abi/aarch64_guard1.C
Date: Wed, 13 Feb 2013 13:32:00 -0000 [thread overview]
Message-ID: <CAFqB+PzGGZXmKpa0JMy2=TPzdMkcxKyVmB=3AdAmuvXkTOXDMA@mail.gmail.com> (raw)
In-Reply-To: <1360762115-23188-1-git-send-email-james.greenhalgh@arm.com>
On 13 February 2013 13:28, James Greenhalgh <james.greenhalgh@arm.com> wrote:
>
> Hi,
>
> If we enable section anchors by default we must fix the
> ABI testcase which is not expecting section anchors.
>
> This was fixed by Andrew Pinski on trunk here:
> http://gcc.gnu.org/ml/gcc-patches/2012-11/msg00580.html
> So we backport that fix.
>
> I've tested this with no regressions on aarch64-none-elf.
>
> Is this OK to commit to aarch64-4.7-branch?
Yes
> gcc/
gcc/testsuite
/Marcus
prev parent reply other threads:[~2013-02-13 13:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 13:28 James Greenhalgh
2013-02-13 13:32 ` Marcus Shawcroft [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='CAFqB+PzGGZXmKpa0JMy2=TPzdMkcxKyVmB=3AdAmuvXkTOXDMA@mail.gmail.com' \
--to=marcus.shawcroft@gmail.com \
--cc=apinski@cavium.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=james.greenhalgh@arm.com \
--cc=marcus.shawcroft@arm.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).