Date: Sun, 2 Apr 2000 09:12:50 +0200 (IST) From: Eli Zaretskii X-Sender: eliz AT is To: broeker AT physik DOT rwth-aachen DOT de cc: djgpp AT delorie DOT com Subject: Re: Gdb and floating point In-Reply-To: <8bstek$iss$1@nets3.rz.RWTH-Aachen.DE> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On 29 Mar 2000 broeker AT physik DOT rwth-aachen DOT de wrote: > pavenis AT lanet DOT lv wrote: > > On 25 Mar 2000, at 22:36, Eli Zaretskii wrote: > [...] > >> One thing I *do* know that GDB 4.18 doesn't handle in the DJGPP port > >> is functions that return FP values in FP registers: it displays > >> garbage as the return value for such functions. GDB 5.0 will corrects > >> this bug. > > > Really? > > > At least I built gdb-20000327 for DJGPP without problems (thanks Eli > > for that) but as I tested problem seems to still be there: > > I cannot inspect floating pount values in function which return > > double in register (p ..., shows something like X.XXXXXe-312) > > That's no what Eli was referring to. He was talking about gdb > displaying the return value, by itself. This happens when you 'call' > the function from gdb, directly, or when you 'finish' it while > stepping through it, IIRC. Yes, that's what I was referring to. Sorry I didn't make it clear. > 3) Check other Intel platforms (Linux, in particular) to see if this > works there. Off the top of my head, I seem to remember it doesn't. > This may imply that the way FPU registers work makes it hard, or even > impossible for gcc to consistently inform gdb about where each of > the variables currently lives. As far as I remember, variables in the FPU registers are indeed unsupported by GDB at the moment, because the compiler doesn't emit enough info for that. I will ask on the GDB development list.