> "JAM" == J A Magallon <[EMAIL PROTECTED]> writes:
JAM> That is not the problem. The problem is that the registers have
JAM> to lay in a defined way, transcribed to a C struct, and that
JAM> pgcc lays badly that struct.
WJP> Yes, I understand that. I was showing a way to find the valu
On 05.18 Bill Pringlemeir wrote:
>> Why don't the build scripts run a dummy file to determine where
>> the floating point registers should be placed?
>>
>> ... const int value = offsetof(struct task_struct,
>> thread.i387.fxsave) & 15; ...
> "JAM" == J A Magallon <[EMAIL PROTECT
On 05.18 Bill Pringlemeir wrote:
>
> Why don't the build scripts run a dummy file to determine where the
> floating point registers should be placed?
>
> ...
> const int value = offsetof(struct task_struct, thread.i387.fxsave) & 15;
> ...
>
That is not the problem. The problem is that the re
> "WJP" == Bill Pringlemeir <[EMAIL PROTECTED]> writes:
[snip]
WJP> I have the 2.4.4 distribution from kernel.org.
WJP> "http://www.kernel.org/pub/linux/kernel/v2.4/";
WJP> I have a Mandrake system and selected the AMD processors and
WJP> APIC option. The egcs-2.91.66 compiler with -mc
Hello,
I have the 2.4.4 distribution from kernel.org.
"http://www.kernel.org/pub/linux/kernel/v2.4/";
I have a Mandrake system and selected the AMD processors and APIC
option. The egcs-2.91.66 compiler with -mcpu=586. It appears that
the structure alignment of the floating point registers
5 matches
Mail list logo