public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
* jmpbuf-offsets.h
@ 2006-01-12  8:26 Thorsten Kukuk
  2006-01-12  9:29 ` jmpbuf-offsets.h Roland McGrath
  0 siblings, 1 reply; 2+ messages in thread
From: Thorsten Kukuk @ 2006-01-12  8:26 UTC (permalink / raw)
  To: libc-hacker


Hi,

what is the plan with jmpbuf-offsets.h? Some architectures have it,
some not. There is a generic one in setjmp/jmpbuf-offsets.h, but
include/bits/setjmp.h cannot find that.

Do we need to add a wrapper to the include directory or do we need to
create this file for every architecture?

  Thorsten

-- 
Thorsten Kukuk         http://www.suse.de/~kukuk/      kukuk@suse.de
SUSE LINUX Products GmbH       Maxfeldstr. 5       D-90409 Nuernberg
--------------------------------------------------------------------    
Key fingerprint = A368 676B 5E1B 3E46 CFCE  2D97 F8FD 4E23 56C6 FB4B

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: jmpbuf-offsets.h
  2006-01-12  8:26 jmpbuf-offsets.h Thorsten Kukuk
@ 2006-01-12  9:29 ` Roland McGrath
  0 siblings, 0 replies; 2+ messages in thread
From: Roland McGrath @ 2006-01-12  9:29 UTC (permalink / raw)
  To: Thorsten Kukuk; +Cc: libc-hacker

It's really only for internal use, so there is no need for architectures to
add one if they have no code that wants it.  I made bits/setjmp.h suck it
only to be lazy and not update the internal uses.  But I forgot that the
stub file would not be found in setjmp.  I've fixed it now to just avoid
the shenanigans and use jmpbuf-offsets.h directly only where it's needed.


Thanks,
Roland

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2006-01-12  9:29 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-01-12  8:26 jmpbuf-offsets.h Thorsten Kukuk
2006-01-12  9:29 ` jmpbuf-offsets.h Roland McGrath

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).