From: Nathan Sidwell <nathan@codesourcery.com>
To: Sam Lauber <sam124@operamail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Unomitted frame pointers
Date: Sat, 11 Dec 2004 16:42:00 -0000 [thread overview]
Message-ID: <41BB2366.80802@codesourcery.com> (raw)
In-Reply-To: <20041211162555.C0BE723CE8@ws5-3.us4.outblaze.com>
Sam Lauber wrote:
> Do you know about macro expansion? CPP would make it seperate strings. So there would be (simplified);
Have you actually TRIED this ?
> int main(void)
> {
> char str1 = "Hello World!\n";
> char str2 = "Hello World!\n";
> int str_len = 0;
> while (*str1++ != "\0")
> str_len++;
> write(2, str2, str_len);
> }
This program won't compile. How do you know what assembly you'd get?
I think you're hypothesizing with no knowledge of the internals of the compiler,
or actual experimentation.
nathan
--
Nathan Sidwell :: http://www.codesourcery.com :: CodeSourcery LLC
nathan@codesourcery.com :: http://www.planetfall.pwp.blueyonder.co.uk
next prev parent reply other threads:[~2004-12-11 16:42 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-11 16:26 Sam Lauber
2004-12-11 16:42 ` Nathan Sidwell [this message]
2004-12-12 0:09 ` Peter Barada
-- strict thread matches above, loose matches on Subject: below --
2004-12-11 16:29 Sam Lauber
2004-12-12 1:33 ` Ian Lance Taylor
2004-12-11 16:15 Sam Lauber
2004-12-11 17:00 ` Eric Botcazou
2004-12-11 18:10 ` Robert Dewar
2004-12-13 6:16 ` Ranjit Mathew
2004-12-13 14:22 ` Robert Dewar
2004-12-13 23:36 ` Ben Elliston
2004-12-11 2:44 Sam Lauber
2004-12-11 15:40 ` Nathan Sidwell
2004-12-11 15:45 ` Andreas Schwab
2004-12-11 2:37 Sam Lauber
2004-12-10 15:44 Thomas R. Truscott
2004-12-10 16:05 ` jlh
2004-12-10 16:25 ` Dave Korn
2004-12-10 16:30 ` Nathan Sidwell
2004-12-10 16:41 ` Dave Korn
2004-12-10 17:54 ` Nathan Sidwell
2004-12-10 16:33 ` Andreas Schwab
2004-12-10 16:40 ` Dave Korn
2004-12-10 16:55 ` Thomas R. Truscott
2004-12-10 17:26 ` Paul Brook
2004-12-11 11:53 ` Kai Henningsen
2004-12-10 5:26 Sam Lauber
2004-12-10 7:22 ` Eric Botcazou
2004-12-10 9:08 ` Richard Guenther
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41BB2366.80802@codesourcery.com \
--to=nathan@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=sam124@operamail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).