Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Mark Kettenis <kettenis@jive.nl>, gdb-patches@sourceware.org
Subject: Re: [commit] Properly cast sentinels for concat()
Date: Tue, 05 Jul 2005 03:34:00 -0000	[thread overview]
Message-ID: <u7jg5q3at.fsf@gnu.org> (raw)
In-Reply-To: <20050704225153.GA31424@nevyn.them.org> (message from Daniel Jacobowitz on Mon, 4 Jul 2005 18:51:53 -0400)

> Date: Mon, 4 Jul 2005 18:51:53 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: Mark Kettenis <kettenis@jive.nl>, gdb-patches@sourceware.org
> 
> You must cast NULL to a pointer type if you use it as the sentinel in a
> varargs list, in portable code, because 0 is a legal definition of NULL
> (according to the C standard, which is quite clear on the subject).  On
> an I32 LP64 system, passing 0 to a varargs function may take 32 bits on
> the stack while passing NULL takes 64 bits.

But in Mark's case, NULL is defined as (void *)0, so it's a pointer,
not an int.

> Even more C++ implementations use 0, which makes the problem even
> worse.  ISTR that (void *)0 is not an acceptable definition of NULL in
> C++.

We are not talking about C++ code here, nor about a C++ compiler.


  reply	other threads:[~2005-07-05  3:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-04 13:36 Mark Kettenis
2005-07-04 22:08 ` Eli Zaretskii
2005-07-04 23:16   ` Andreas Schwab
2005-07-05  1:32   ` Daniel Jacobowitz
2005-07-05  3:34     ` Eli Zaretskii [this message]
2005-07-05  4:23       ` Daniel Jacobowitz
2005-07-05  7:30       ` Mark Kettenis
2005-07-05 20:03         ` Eli Zaretskii
2005-07-05  7:36   ` Mark Kettenis

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=u7jg5q3at.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=kettenis@jive.nl \
    /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