--- Comment #17 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Jiri Slaby from comment #16)
> (In reply to Jakub Jelinek from comment #15)
> > lots of them that rely on pointer arithmetics being defined only within the
> > same object.
> Sure, but the two pointers (taken implicitly of the arrays) are within the
> same object. So I do not see, why it wouldn't work? I.e. where exactly this
> breaks the C specs?
No. In C
extern struct builtin_fw __start_builtin_fw;
extern struct builtin_fw __end_builtin_fw;
declares two external arrays, thus they are two independent objects. It is
like if you have:
in your program, although they might be allocated adjacent, such that
int *p = &a; int *q = &b; memcmp (&p, &q, sizeof (p)) == 0;
&b - &a is still UB.
What you do with __start_*/__end_* symbols is nothing you can define in C, you
need linker support or asm for that, and to use it without UB you also need to
use an optimization barrier that has been suggested.