This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Unomitted frame pointers
- From: "Sam Lauber" <sam124 at operamail dot com>
- To: "Andreas Schwab" <schwab at suse dot de>, gcc at gcc dot gnu dot org
- Date: Sat, 11 Dec 2004 17:29:35 +0100
- Subject: Re: Unomitted frame pointers
How can the linker combine them? The _program_ is way outside GCC's control. The assembler and linker don't modify the generated assembly. Otherwise, BFD and binutils would become very twisted up, and thus make the assembler world on GCC diffrent than it is now.
----- Original Message -----
From: "Andreas Schwab" <schwab@suse.de>
To: "Sam Lauber" <sam124@operamail.com>
Subject: Re: Unomitted frame pointers
Date: Sat, 11 Dec 2004 16:44:54 +0100
>
> "Sam Lauber" <sam124@operamail.com> writes:
>
> > We would end up with two copies of the string. #defines are
> > preprocessed, so it would expand to the second thing.
>
> And the compiler and the linker combine them again.
>
> > The _safe_ way to do it is
> >
> > char str = "Hello World!\n";
> > write(2, str, strlen(str)-1);
>
> Why would you want to exclude the trailing newline?
>
> Andreas.
>
> --
> Andreas Schwab, SuSE Labs, schwab@suse.de
> SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
> Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
> "And now for something completely different."
--
_____________________________________________________________
Web-based SMS services available at http://www.operamail.com.
From your mailbox to local or overseas cell phones.
Powered by Outblaze