From: jlh <jlh@gmx.ch>
To: "Thomas R. Truscott" <trt@cs.duke.edu>
Cc: gcc@gcc.gnu.org
Subject: Re: Unomitted frame pointers
Date: Fri, 10 Dec 2004 16:05:00 -0000 [thread overview]
Message-ID: <41B9C91A.8020405@gmx.ch> (raw)
In-Reply-To: <200412101544.iBAFiC0P004241@eenie.cs.duke.edu>
[-- Attachment #1: Type: text/plain, Size: 399 bytes --]
> Off-topic, but the hello.c program does:
> write(2, "Hello World!\n\0", 16);
> The string length is 15, not 16.
15 is what gets allocated for storing the string (counting
the additional \0 that always gets appened to string constants).
But neither the explicit nor the implicit \0 should be printed
to the console, so the call should definitely read:
write(2, "Hello World!\n", 13);
jlh
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2004-12-10 16:05 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-10 15:44 Thomas R. Truscott
2004-12-10 16:05 ` jlh [this message]
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 18:09 ` [OT] " Dave Korn
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
-- 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:26 Sam Lauber
2004-12-11 16:42 ` Nathan Sidwell
2004-12-12 0:09 ` Peter Barada
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 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=41B9C91A.8020405@gmx.ch \
--to=jlh@gmx.ch \
--cc=gcc@gcc.gnu.org \
--cc=trt@cs.duke.edu \
/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).