This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.

Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: makecontext and its arguments

From: Andreas Jaeger <aj at suse dot de>
To: Ulrich Drepper <drepper at redhat dot com>
Cc: Andreas Schwab <schwab at suse dot de>,GNU libc hacker <libc-hacker at sources dot redhat dot com>
Date: Mon, 05 Aug 2002 19:10:06 +0200
Subject: Re: makecontext and its arguments
References: <u8elddip92.fsf@gromit.moeb> <jeptwxv81s.fsf@sykes.suse.de><3D4EACF8.2000901@redhat.com>

Ulrich Drepper <drepper@redhat.com> writes:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Andreas Schwab wrote:
>
>> IMHO this is a defect in the standard, because "integer" can mean
>> anything from char to long long and whatever extended integer type might
>> be defined.  It does not restrict the arguments to type "int".
>
> I tend to agree.  We use long for that reason.  It's the most useful
> interpretation of "integer".

That interpretation of long causes problems for x86-64 since ints are
not sign extented when passed in varargs...

So, what can I do?

Andreas
-- 
 Andreas Jaeger
  SuSE Labs aj@suse.de
   private aj@arthur.inka.de
    http://www.suse.de/~aj

Follow-Ups:
- Re: makecontext and its arguments
  - From: Ulrich Drepper

References:
- makecontext and its arguments
  - From: Andreas Jaeger
- Re: makecontext and its arguments
  - From: Andreas Schwab
- Re: makecontext and its arguments
  - From: Ulrich Drepper

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]