Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: pierre.muller@ics-cnrs.unistra.fr, gdb-patches@sourceware.org
Subject: Re: [RFC] Fix for Go32-v2 native woes
Date: Wed, 07 Apr 2010 03:23:00 -0000	[thread overview]
Message-ID: <83wrwkvtbk.fsf@gnu.org> (raw)
In-Reply-To: <201004061841.o36If19m004817@glazunov.sibelius.xs4all.nl>

> Date: Tue, 6 Apr 2010 20:41:01 +0200 (CEST)
> From: Mark Kettenis <mark.kettenis@xs4all.nl>
> CC: pierre.muller@ics-cnrs.unistra.fr, gdb-patches@sourceware.org
> 
> > Why do we always read i386-sse.xml or assume that SSE is supported?
> > We should not assume any CPU features by default if there are CPUs out
> > there which we support that don't have them.
> 
> Because that basically was the situation before.

I'm not sure I follow.  GDB 7 builds and works in the DJGPP port
without any trouble, even though SSE support was there before, wasn't
it?

> When SSE support was addid we didn't really have a way to detect
> whether a target supported SSE or not.

Well, then it should be part of the target configuration.

> Does Go32 really have no support for the SSE registers?

Yes, really.  The debug interface provided by DPMI (the interface for
running protected-mode programs on DOS, which is a real-mode OS) does
not support SSE.  And since no one is developing the DPMI spec or DPMI
ser5vices these days, SSE will never be supported by DJGPP.  In fact,
none of the special registers of the modern x86 CPUs (XMM etc.) will
ever be supported.

Therefore, the fact that SSE is not supported by DJGPP can be
established at compile time.


  reply	other threads:[~2010-04-07  3:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
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
2010-04-06 17:48 ` Eli Zaretskii
     [not found] <1242886820451223367@unknownmsgid>
2010-04-07  6:32 ` [RFC] Fix for " H.J. Lu
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>
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=83wrwkvtbk.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    --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