From: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>
To: Wilco Dijkstra <Wilco.Dijkstra@arm.com>,
James Greenhalgh <James.Greenhalgh@arm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, nd <nd@arm.com>,
Marcus Shawcroft <Marcus.Shawcroft@arm.com>
Subject: Re: [PATCH v3][AArch64] Fix symbol offset limit
Date: Thu, 15 Jun 2017 18:34:00 -0000 [thread overview]
Message-ID: <067b75ca-f8e0-3bc6-c344-fc92aa2babe6@arm.com> (raw)
In-Reply-To: <AM5PR0802MB26102767EB8801FC0D3CA91883C00@AM5PR0802MB2610.eurprd08.prod.outlook.com>
On 15/06/17 19:18, Wilco Dijkstra wrote:
> Richard Earnshaw wrote:
>
> C11: Summary of undefined behaviours.
>
> — Addition or subtraction of a pointer into, or just beyond, an array
> object and an
> integer type produces a result that does not point into, or just beyond,
> the same array
> object (6.5.6).
>
> That's totally irrelevant given the addition is created by the optimizer.
>
> Wilco
>
No it's not. The optimizer doesn't create totally random bases. If the
code + data is less than 1M in size, then any offsets it does create
will fit within the size of the relocations selected by the compiler.
R.
next prev parent reply other threads:[~2017-06-15 18:34 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 14:11 [PATCH][AArch64] " Wilco Dijkstra
2016-08-26 10:43 ` Richard Earnshaw (lists)
2016-08-26 19:07 ` Wilco Dijkstra
2016-09-12 15:30 ` [PATCH v2][AArch64] " Wilco Dijkstra
2016-09-21 14:48 ` Wilco Dijkstra
2016-10-17 12:42 ` Wilco Dijkstra
2016-10-25 9:47 ` Wilco Dijkstra
2016-11-02 16:48 ` Wilco Dijkstra
2016-11-14 13:07 ` Wilco Dijkstra
2016-12-06 15:07 ` Wilco Dijkstra
2017-01-17 15:14 ` [PATCH v3][AArch64] " Wilco Dijkstra
2017-02-02 14:44 ` Wilco Dijkstra
2017-02-23 16:58 ` Wilco Dijkstra
2017-04-20 16:03 ` Wilco Dijkstra
2017-06-13 14:00 ` Wilco Dijkstra
2017-06-14 14:07 ` James Greenhalgh
2017-06-14 16:03 ` Wilco Dijkstra
2017-06-15 15:13 ` Richard Earnshaw (lists)
2017-06-15 16:55 ` Wilco Dijkstra
2017-06-15 17:39 ` Richard Earnshaw (lists)
2017-06-15 17:51 ` Wilco Dijkstra
2017-06-15 18:11 ` Richard Earnshaw (lists)
2017-06-15 18:18 ` Wilco Dijkstra
2017-06-15 18:34 ` Richard Earnshaw (lists) [this message]
2017-06-15 18:55 ` Wilco Dijkstra
2017-06-15 19:52 ` Joseph Myers
2017-06-16 15:14 ` Nathan Sidwell
2017-06-27 15:36 ` Wilco Dijkstra
2017-07-14 14:28 ` Wilco Dijkstra
2017-07-21 11:23 ` Wilco Dijkstra
2017-08-01 10:19 ` Wilco Dijkstra
2017-08-15 17:36 ` Wilco Dijkstra
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=067b75ca-f8e0-3bc6-c344-fc92aa2babe6@arm.com \
--to=richard.earnshaw@arm.com \
--cc=James.Greenhalgh@arm.com \
--cc=Marcus.Shawcroft@arm.com \
--cc=Wilco.Dijkstra@arm.com \
--cc=gcc-patches@gcc.gnu.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).