>>>'what' is broken. C does not impose any sort of address ordering
>>>restriction on globals or autos that are declared next to each other.
> Right, except that 'what' isn't broken. It is vers.c (and conf/newvers.sh)
> that is broken, believing that the two variables will be allocating in
> con
On Tue, 6 Apr 1999, Bruce Evans wrote:
> >Alternately, we could jimmy around with the current hack, and prefix it
> >with 4 NULs, and see what happened. Sorry, I haven't tested this idea, as
> >I've not yet made the EGCS jump.
>
> egcs aligns long (>= about 28 bytes) strings to 32-byte boundar
> The real question is whether the extreme alignment and padding used by
> EGCS can be turned off, especially for 486s.
Considering it... probably based on -m486.
--
-- David(obr...@nuxi.com -or- obr...@freebsd.org)
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe fr
> 'what' is broken. C does not impose any sort of address ordering
> restriction on globals or autos that are declared next to each other.
Right, except that 'what' isn't broken. It is vers.c (and conf/newvers.sh)
that is broken, believing that the two variables will be allocating in
co
>Alternately, we could jimmy around with the current hack, and prefix it
>with 4 NULs, and see what happened. Sorry, I haven't tested this idea, as
>I've not yet made the EGCS jump.
egcs aligns long (>= about 28 bytes) strings to 32-byte boundaries. This
adds up to 27 NULs to sccsid[] depending
On Monday, 5th April 1999, Matthew Dillon wrote:
>:char sccs[] = { '@', '(', '#', ')' };
>:char version[] = blahhhfoo;
>:Was contiguous.
>'what' is broken. C does not impose any sort of address ordering
>restriction on globals or autos that are declared next to each other.
Well,
: Okay, let me be a little clearer ;) What(1) on the kernel no longer works
:because previously, the
:char sccs[] = { '@', '(', '#', ')' };
:char version[] = blahhhfoo;
:Was contiguous. However, nowadays, nice EGCS pads 4 bytes (WHY?!?!) between
:those. So it appears "@(#)\0\0\0\0FreeBSD.
Okay, let me be a little clearer ;) What(1) on the kernel no longer works
because previously, the
char sccs[] = { '@', '(', '#', ')' };
char version[] = blahhhfoo;
Was contiguous. However, nowadays, nice EGCS pads 4 bytes (WHY?!?!) between
those. So it appears "@(#)\0\0\0\0FreeBSD." in t
