X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
From: Rugxulo <rugxulo AT gmail DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Please help resurrecting GDB for version 7.0 release
Date: Sun, 3 May 2009 08:07:31 -0700 (PDT)
Organization: http://groups.google.com
Lines: 46
Message-ID: <81b25848-18e8-48df-86c6-ac43943d856c@r34g2000vbi.googlegroups.com>
References: <83zldveryw DOT fsf AT gnu DOT org> <684bdd55-b464-4e61-b28e-28774dc6ced8 AT o27g2000vbd DOT googlegroups DOT com> 
	<83y6tfem02 DOT fsf AT gnu DOT org> <_ZKdnV74euw2-2HUnZ2dnUVZ_uednZ2d AT earthlink DOT com> 
	<83ws8zeb05 DOT fsf AT gnu DOT org>
NNTP-Posting-Host: 65.13.115.246
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Trace: posting.google.com 1241363252 32486 127.0.0.1 (3 May 2009 15:07:32 GMT)
X-Complaints-To: groups-abuse AT google DOT com
NNTP-Posting-Date: Sun, 3 May 2009 15:07:32 +0000 (UTC)
Complaints-To: groups-abuse AT google DOT com
Injection-Info: r34g2000vbi.googlegroups.com; posting-host=65.13.115.246; 
	posting-account=p5rsXQoAAAB8KPnVlgg9E_vlm2dvVhfO
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.10) 
	Gecko/2009042316 Firefox/3.0.10 (.NET CLR 3.5.30729),gzip(gfe),gzip(gfe)
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Hi,

On May 2, 11:16=A0am, Eli Zaretskii <e DOT  DOT  DOT  AT gnu DOT org> wrote:
> > From: "Charles Sandmann" <cwsd DOT  DOT  DOT  AT earthlink DOT net>
> > Date: Sat, 2 May 2009 10:28:29 -0500
>
> > >"Eli Zaretskii" <e DOT  DOT  DOT  AT gnu DOT org> wrote in message
> > >news:83y6tfem02 DOT fsf AT gnu DOT org...
> > >> From: Rugxulo <rugx DOT  DOT  DOT  AT gmail DOT com>
> > >> It also doesn't like "info all-regs", IIRC.
> > >Yes, for the same reason: it thinks DJGPP supports SSE registers.
>
> > What is required to make that work?
>
> There are 2 possible fixes: the easy one and the more complicated one.
>
> The easy one is a two-liner: tell GDB that we don't support SSE. =A0I
> already did that, and the patch is in the GDB CVS repository since
> about 2 days ago. =A0(The original problem happened because GDB switched
> to supporting SSE by default in its x86 targets at some point, so any
> target that doesn't support them needs to explicitly disable that.
> Seems like no one from the DJGPP camp, yours truly included, payed
> attention at the time.)

Well, I agree it's probably not a priority. Nevertheless, it can't be
that hard to do, can it? DJ could probably tell us more.

> The more complex solution is to extend save_npx and load_npx to use
> FXSAVE and FXRSTOR instructions, when they are available, instead of
> FNSAVE and FRSTOR that we use now. =A0But that means hacking the library
> or providing GDB-private versions of these functions. =A0

I've heard that FX* are faster, if that makes you feel any better.

BTW, GNU Emacs still carries around two replacement files for bugs in
DJGPP 2.00, so this wouldn't be so strange.

> Unless many
> DJGPP users need access to SSE registers (which sounds improbable,
> given that this feature is badly broken for at least 5 last years), I
> don't see a justification for this hassle.

There are some projects that can use SSE (e.g. libmpeg2, fftw, liboil,
sseplus, paq7 / paq8, FreeBASIC). And CWSDPMI (and HDPMI32) enable it
for us, if needed. So it's not like it wouldn't be nice, but since I
don't know how to do it myself, it's your call.     ;-)