Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Fix for Go32-v2 native woes
Date: Wed, 07 Apr 2010 06:32:00 -0000	[thread overview]
Message-ID: <m2g6dc9ffc81004062332i772781edjc1a3ef9d761f12f4@mail.gmail.com> (raw)
In-Reply-To: <1242886820451223367@unknownmsgid>

On Tue, Apr 6, 2010 at 7:15 AM, Pierre Muller
<pierre.muller@ics-cnrs.unistra.fr> wrote:
>  In an email to gdb list,
> I complained about go32 native GDB giving internal errors...
>
>  The problem is that some code in i386-tdep.c is not compatible
> with a target that supports no SSE registers.
>
>  I finally managed to find a fix, but it is not straightforward:
>  I had to add a new xml file in features/i386 directory
> specific for go32v2 target, that does not read i386-sse.xml.
>  I had to adapt the code in i386-tdep.c to support
> missing feature_vector and to set tdesc to
> tdesc_i386_go32v2 instead of tdesc_i386 when go32v2
> osabi was detected.
>
>  This allows me to use CVS GDB on DJGPP again.
>
>  I checked with a testsuite run on gcc-farm that nothing changed
> for at least that other target (amd64-linux).
>
>  Similar fixes might be required for other 'old'
> i386 targets that do not support SSE registers.
>
>  Comments welcome as usual!
>
> Pierre Muller
> Pascal language support maintainer for GDB
>
>
>
> 2010-04-06  Pierre Muller  <muller@ics.u-strasbg.fr>
>
>        * i386-tdep.c: Add include features/i386/i386-go32v2.c.
>        (i386_go32_init_abi): Set TDESC field to TDESC_I386_GO32V2.
>        (i386_validate_tdesc_p): Do not require FEATURE_VECTOR.
>        Adapt code accordingly.
>        (i386_gdbarch_init): Set TDESC to TDESC_I386_GO32V2 if
>        os abi is GDB_OSABI_GO32V2.
>        (_initialize_i386_tdep): Call initialize_tdes_i386_go32v2 function.
>
>        * features/Makefile (WHICH): Add new i386/i386-go32v2 entry.
>        * features/i386/i386-go32v2.xml: New file. Without SSE regsiters.
>        * features/i386/i386-go32v2.c: New generated file.
>        * regformats/i386/i386-go32v2.dat: New generated file.
>

This patch is incorrect. Linux runs on 32bit x86 processors without SSE.
I have a patch to support it.

-- 
H.J.


       reply	other threads:[~2010-04-07  6:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1242886820451223367@unknownmsgid>
2010-04-07  6:32 ` H.J. Lu [this message]
2010-04-07 17:35   ` H.J. Lu
2010-04-07 17:53     ` Eli Zaretskii
2010-04-07 18:01       ` H.J. Lu
     [not found] <002a01cad517$d36eab90$7a4c02b0$%muller@ics-cnrs.unistra.fr>
     [not found] ` <001801cad593$8e70daf0$ab5290d0$%muller@ics-cnrs.unistra.fr>
2010-04-06 17:46   ` Eli Zaretskii
2010-04-06 18:41     ` Mark Kettenis
2010-04-07  3:23       ` Eli Zaretskii
2010-04-07  3:20     ` Eli Zaretskii
2010-04-07  6:19       ` H.J. Lu
2010-04-07  6:44         ` Eli Zaretskii
2010-04-07 14:41           ` Daniel Jacobowitz
2010-04-07 17:34             ` Eli Zaretskii
2010-04-07 17:37               ` H.J. Lu
     [not found] <002a01cad517$d36eab90$7a4c02b0$@muller@ics-cnrs.unistra.fr>
2010-04-06 14:15 ` Pierre Muller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2g6dc9ffc81004062332i772781edjc1a3ef9d761f12f4@mail.gmail.com \
    --to=hjl.tools@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pierre.muller@ics-cnrs.unistra.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox