From: Yvan Roux <yvan.roux@linaro.org>
To: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
"kugan.vivekanandarajah@linaro.org"
<kugan.vivekanandarajah@linaro.org>, nd <nd@arm.com>,
James Greenhalgh <James.Greenhalgh@arm.com>,
Richard Earnshaw <Richard.Earnshaw@arm.com>
Subject: Re: [AARCH64] Disable pc relative literal load irrespective of TARGET_FIX_ERR_A53_84341
Date: Fri, 11 Aug 2017 13:08:00 -0000 [thread overview]
Message-ID: <CAD57uCfYt6KKaDYZ=99nPcnKZvXtYA60Q1TO7Oi_ThGSMVU0zw@mail.gmail.com> (raw)
In-Reply-To: <DB6PR0801MB20536262D2C32C62D6EDF83983890@DB6PR0801MB2053.eurprd08.prod.outlook.com>
On 11 August 2017 at 13:50, Wilco Dijkstra <Wilco.Dijkstra@arm.com> wrote:
> Kugan wrote:
>> Ping^2?
>
> Could you make sure to either include the patch or provide a link to it?
> (https://gcc.gnu.org/ml/gcc-patches/2017-06/msg01967.html)
>
> I think the patch is fine since avoiding adrp/ldr on literals doesn't really
> help when global variables still use adrp. If you really want to avoid adrp
> and don't care about the overhead, there is -mcmodel=large...
>
> Note once you get the OK, we should consider backporting this with
> https://gcc.gnu.org/ml/gcc-patches/2017-08/msg00386.html.
good point Wilco, I'll take care to add to the backport when it'll be accepted.
> Wilco
next prev parent reply other threads:[~2017-08-11 12:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 13:07 Wilco Dijkstra
2017-08-11 13:08 ` Yvan Roux [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-06-27 1:20 Kugan Vivekanandarajah
2017-06-27 8:01 ` Ramana Radhakrishnan
2017-06-28 1:02 ` Kugan Vivekanandarajah
2017-06-28 22:06 ` Ramana Radhakrishnan
2017-07-21 10:12 ` Kugan Vivekanandarajah
2017-08-11 10:34 ` Kugan Vivekanandarajah
2017-08-29 8:32 ` Kugan Vivekanandarajah
2017-08-29 12:02 ` James Greenhalgh
2017-08-30 9:05 ` Kugan Vivekanandarajah
2018-03-07 1:59 ` Kugan Vivekanandarajah
2018-03-07 10:35 ` James Greenhalgh
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='CAD57uCfYt6KKaDYZ=99nPcnKZvXtYA60Q1TO7Oi_ThGSMVU0zw@mail.gmail.com' \
--to=yvan.roux@linaro.org \
--cc=James.Greenhalgh@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=Wilco.Dijkstra@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kugan.vivekanandarajah@linaro.org \
--cc=nd@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).