Article View: comp.arch
Article #12902Re: Aliasing, etc. in C (available no. of registers)
From: radford
Date: Tue, 27 Jan 1987 18:52
Date: Tue, 27 Jan 1987 18:52
21 lines
1258 bytes
1258 bytes
In article <7803@decwrl.DEC.COM>, brandenberg@star.dec.com (bleakness...desolation...plastic forks...) writes:
> >> int a,b, *ptr;
> >>
> >> ptr = &a;
> >> ptr++;
> >> /* ptr now points to b */
> >
> >No program that relies on that is correct C...
>
> Oh? If this is aberrant coding, you might want to look at your
> varargs.h file whose operation relies on these assumptions; and this is
> in the ANSI proposal.
As I understand it, the ANSI proposal specifies that the FUNCTION of
varargs.h must exist, not that the particular varargs.h source file
you are looking at must work. Indeed, there would be no point in mentioning
varargs.h in the standard if the code it contained was guaranteed to
work on all machines.
Radford Neal
Technical Details
Message-ID:
<771@vaxb.calgary.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!watmath!clyde!cbatt!ihnp4!alberta!calgary!radfordReferences:
<7803@decwrl.DEC.COM>Show Full Headers
Complete Article Headers
Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: arc1-ca.pugleaf.net!utzoo!watmath!clyde!cbatt!ihnp4!alberta!calgary!radford From: radford@calgary.UUCP Newsgroups: comp.arch Subject: Re: Aliasing, etc. in C (available no. of registers) Message-ID: <771@vaxb.calgary.UUCP> Date: Tue, 27-Jan-87 13:52:04 EST Article-I.D.: vaxb.771 Posted: Tue Jan 27 13:52:04 1987 Date-Received: Fri, 30-Jan-87 05:24:29 EST References: <7803@decwrl.DEC.COM> Organization: U. of Calgary, Calgary, Ab. Lines: 21