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: Versioning longjmp etc.

From: Steve Munroe <sjmunroe at us dot ibm dot com>
To: Ulrich Drepper <drepper at redhat dot com>
Cc: libc-hacker at sources dot redhat dot com, sjmunroe at vnet dot ibm dot com
Date: Fri, 17 Oct 2003 16:12:19 -0500
Subject: Re: Versioning longjmp etc.

Ulrich Drepper writes:

> Why should this be necessary?  It makes almost no sense at all to
> include the content of these registers in the state. setjmp/longjmp are
> probably never used in the middle of computations in which vector
> registers are used.

For the future when gcc supports autovectorization.

I want to make VMX as usable as possible, without undefined behaviors or 
undocumented restrictions. 

How about get/set/make/swapcontext? The size of ucontext will change as a 
result of VMX state in sigcontext. This requires versioning.

Follow-Ups:
- Re: Versioning longjmp etc.
  - From: Ulrich Drepper

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