Kumar Gala wrote:
>
> On Oct 11, 2007, at 2:15 AM, [EMAIL PROTECTED] wrote:
>
>> Replace NT_PRXFPREG with ELF_CORE_XFPREG_TYPE in the coredump code which
>> allows for more flexibility in the note type for the state of 'extended
>> floating point' implementations in coredumps. New note types can
On Thu, 2007-10-11 at 08:04 -0500, Kumar Gala wrote:
> On Oct 11, 2007, at 2:15 AM, [EMAIL PROTECTED] wrote:
>
> > Replace NT_PRXFPREG with ELF_CORE_XFPREG_TYPE in the coredump code
> > which
> > allows for more flexibility in the note type for the state of
> > 'extended
> > floating point'
Kumar Gala writes:
> > ELF_CORE_XFPREG_TYPE is a suitable name for something that's used in
> > conjunction with a function called elf_core_copy_task_xfpregs().
>
> agreed, I think the function name should change as well.
Maybe. Let's do one step at a time...
Paul.
-
To unsubscribe from this
On Oct 11, 2007, at 4:55 PM, Paul Mackerras wrote:
Kumar Gala writes:
#define ELF_CORE_XFPREG_TYPE to be NT_PRXFPREG in all current
users so
there's are no change in behaviour.
Can we make this ELF_CORE_VECREG_TYPE or something that is so coupled
to the x86 specific name?
How is
Kumar Gala writes:
> > #define ELF_CORE_XFPREG_TYPE to be NT_PRXFPREG in all current users so
> > there's are no change in behaviour.
>
> Can we make this ELF_CORE_VECREG_TYPE or something that is so coupled
> to the x86 specific name?
How is "extended floating point registers" x86-specific?
On Oct 11, 2007, at 2:15 AM, [EMAIL PROTECTED] wrote:
Replace NT_PRXFPREG with ELF_CORE_XFPREG_TYPE in the coredump code
which
allows for more flexibility in the note type for the state of
'extended
floating point' implementations in coredumps. New note types can
now be
added with an
On Oct 11, 2007, at 2:15 AM, [EMAIL PROTECTED] wrote:
Replace NT_PRXFPREG with ELF_CORE_XFPREG_TYPE in the coredump code
which
allows for more flexibility in the note type for the state of
'extended
floating point' implementations in coredumps. New note types can
now be
added with an
Kumar Gala writes:
#define ELF_CORE_XFPREG_TYPE to be NT_PRXFPREG in all current users so
there's are no change in behaviour.
Can we make this ELF_CORE_VECREG_TYPE or something that is so coupled
to the x86 specific name?
How is extended floating point registers x86-specific?
On Oct 11, 2007, at 4:55 PM, Paul Mackerras wrote:
Kumar Gala writes:
#define ELF_CORE_XFPREG_TYPE to be NT_PRXFPREG in all current
users so
there's are no change in behaviour.
Can we make this ELF_CORE_VECREG_TYPE or something that is so coupled
to the x86 specific name?
How is
Kumar Gala writes:
ELF_CORE_XFPREG_TYPE is a suitable name for something that's used in
conjunction with a function called elf_core_copy_task_xfpregs().
agreed, I think the function name should change as well.
Maybe. Let's do one step at a time...
Paul.
-
To unsubscribe from this list:
On Thu, 2007-10-11 at 08:04 -0500, Kumar Gala wrote:
On Oct 11, 2007, at 2:15 AM, [EMAIL PROTECTED] wrote:
Replace NT_PRXFPREG with ELF_CORE_XFPREG_TYPE in the coredump code
which
allows for more flexibility in the note type for the state of
'extended
floating point'
Kumar Gala wrote:
On Oct 11, 2007, at 2:15 AM, [EMAIL PROTECTED] wrote:
Replace NT_PRXFPREG with ELF_CORE_XFPREG_TYPE in the coredump code which
allows for more flexibility in the note type for the state of 'extended
floating point' implementations in coredumps. New note types can now be
12 matches
Mail list logo
