musl - RE: Need "_fpx_sw_bytes", "FP_XSTATE_MAGIC2_SIZE" and "FP_XSTATE_MAGIC{1,2}" definition to compile CoreCLR

Follow @Openwall on Twitter for new release announcements and other news

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <HE1PR83MB0058482A216771755501A4B0CAC00@HE1PR83MB0058.EURPRD83.prod.outlook.com>
Date: Sat, 1 Oct 2016 10:28:08 +0000
From: Jan Vorlicek <janvorli@...rosoft.com>
To: Rich Felker <dalias@...c.org>, "musl@...ts.openwall.com"
	<musl@...ts.openwall.com>
Subject: RE: Need "_fpx_sw_bytes", "FP_XSTATE_MAGIC2_SIZE" and
 "FP_XSTATE_MAGIC{1,2}" definition to compile CoreCLR

In addition to that, we would also need the _xstate struct (and obviously also the structs it refers to, like _ymmh_state, _xsave_hdr, ...). 
We only need that for x64.

Thanks,

Jan

-----Original Message-----
From: Rich Felker [mailto:dalias@...c.org] 
Sent: Tuesday, August 30, 2016 11:43 PM
To: musl@...ts.openwall.com
Subject: Re: [musl] Need "_fpx_sw_bytes", "FP_XSTATE_MAGIC2_SIZE" and "FP_XSTATE_MAGIC{1,2}" definition to compile CoreCLR

On Thu, Aug 04, 2016 at 09:15:40PM +0000, Dangling Pointer wrote:
> Please provide the user-facing definitions of "struct _fpx_sw_bytes" and macros "FP_XSTATE_MAGIC2_SIZE", "FP_XSTATE_MAGIC1" and "FP_XSTATE_MAGIC2" to compile CoreCLR.
> 
> 
> Related issue: 
> https://github.com/dotnet/coreclr/issues/917#issuecomment-236907708
> 
> Usage:  
> https://github.com/dotnet/coreclr/blob/9585fc2/src/pal/src/include/pal
> /context.h#L142-L178

Would a patch like the attached me sufficient? Does 32-bit x86 need something like this too?

Rich

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.