This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Assignment operator
Zoltan Kocsi <zoltan@bendor.com.au> writes:
|> Well, this is not exactly true. strcpy() has nothing to do with
|> volatile but it is defined to stop when the '\0' in the *source*
|> string is processed. Egcs for m68k target, *without* volatile
|> qualifier (it generates the exact same code with it too):
If you pass a volatile pointer to strcpy you move outside the realms of
the standard. That's what is called undefined behaviour.
Andreas.
--
Andreas Schwab "And now for something
SuSE Labs completely different."
schwab@suse.de
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg