From: Segher Boessenkool <segher@kernel.crashing.org>
To: Ian Lance Taylor <ian@airs.com>
Cc: "Alex J. Dam" <alexjdam@gmail.com>,
GCC-Help <gcc-help@gcc.gnu.org>,
ernesto@ornl.gov
Subject: Re: Moving to AMD64 bit and porting issues
Date: Fri, 04 Nov 2005 11:54:00 -0000 [thread overview]
Message-ID: <61a69f794d1144ba9db3959d2f043afb@kernel.crashing.org> (raw)
In-Reply-To: <m3wtk23fiq.fsf@gossamer.airs.com>
> You can reliably use 0 as a null pointer constant with one exception.
> When calling a varargs function which expects a pointer as an unnamed
> argument, and when pointers are 64-bits but int is 32-bits, then you
> must either use NULL or you must cast 0 to a pointer type.
Using NULL in this case is not portable; you *must*
use a cast to the exact pointer type that the
varargs function expects to see. Different pointer
types can have different representation.
Segher
next prev parent reply other threads:[~2005-11-04 11:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-22 5:26 Ernest L. Williams Jr.
2005-10-24 10:24 ` Alex J. Dam
2005-10-24 10:33 ` random
2005-10-24 10:37 ` Ernest L. Williams Jr.
2005-10-24 19:02 ` Ian Lance Taylor
2005-11-04 11:54 ` Segher Boessenkool [this message]
2005-11-04 12:05 ` Ernest L. Williams Jr.
2005-11-04 12:35 ` Segher Boessenkool
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=61a69f794d1144ba9db3959d2f043afb@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=alexjdam@gmail.com \
--cc=ernesto@ornl.gov \
--cc=gcc-help@gcc.gnu.org \
--cc=ian@airs.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).