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: thread-ready ABIs

From: Andreas Schwab <schwab at suse dot de>
To: drepper at redhat dot com (Ulrich Drepper)
Cc: GNU libc hacker <libc-hacker at sources dot redhat dot com>
Date: Fri, 18 Jan 2002 17:10:43 +0100
Subject: Re: thread-ready ABIs
References: <m3elkoa5dw.fsf@myware.mynet> <je3d1329l7.fsf@sykes.suse.de><m3it9z63s7.fsf@myware.mynet>

Ulrich Drepper <drepper@redhat.com> writes:

|> Andreas Schwab <schwab@suse.de> writes:
|> 
|> > None of the address registers are useless, they are all needed.  Reserving
|> > one of them as a thread register means an ABI change, since currently all
|> > (address or data) registers are either scratch or callee-saved.
|> 
|> And this means?  Make a decision.  Will you break the ABI or never
|> have a thread register?

I have raised the issue on the linux-m68k mailinglist.  Let's see what
they say about this.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE GmbH, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

References:
- thread-ready ABIs
  - From: Ulrich Drepper
- Re: thread-ready ABIs
  - From: Andreas Schwab
- Re: thread-ready ABIs
  - From: Ulrich Drepper

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