summaryrefslogtreecommitdiffstats
path: root/lib/libc/string/stpcpy.c
diff options
context:
space:
mode:
authormarcel <marcel@FreeBSD.org>2003-03-05 04:39:24 +0000
committermarcel <marcel@FreeBSD.org>2003-03-05 04:39:24 +0000
commitd4ee62b07a76bf06911d862a0e2084a2309efa36 (patch)
tree43c9fbba16caef13b08438e9431452fba63c0dde /lib/libc/string/stpcpy.c
parentcf2b37334bdcf41af17a17f34a5d80417cc188d8 (diff)
downloadFreeBSD-src-d4ee62b07a76bf06911d862a0e2084a2309efa36.zip
FreeBSD-src-d4ee62b07a76bf06911d862a0e2084a2309efa36.tar.gz
Fix threaded applications on ia64 that are linked dynamicly. We did
not save (restore) the global pointer (GP) in the jmpbuf in setjmp (longjmp) because it's not needed in general. GP is considered a scratch register at callsites and hence is always restored after a call (when it's possible that the call resolves to a symbol in a different loadmodule; otherwise GP does not have to be saved and restored at all), including calls to setjmp/longjmp. There's just one problem with this now that we use setjmp/longjmp for context switching: A new context must have GP defined properly for the thread's entry point. This means that we need to put GP in the jmpbuf and consequently that we have to restore is in longjmp. This automaticly requires us to save it as well. When setjmp/longjmp isn't used for context switching, this can be reverted again.
Diffstat (limited to 'lib/libc/string/stpcpy.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud