From: "Maciej W. Rozycki" <macro@codesourcery.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH] AArch64: gdb.base/float.exp: Fix `info float' test
Date: Wed, 15 Jan 2014 08:27:00 -0000 [thread overview]
Message-ID: <alpine.DEB.1.10.1401150815500.6899@tp.orcam.me.uk> (raw)
In-Reply-To: <20140115034527.GH4762@adacore.com>
On Wed, 15 Jan 2014, Joel Brobecker wrote:
> > gdb/testsuite/
> > * gdb.base/float.exp: Handle "aarch64*-*-*" targets.
>
> FWIW, no problem with the patch. But I don't know AArch64.
> Does it always have an FPU? Otherwise, we perhaps should look at
> what is being done for arm-*?
Hard to tell, this popped up in testing, but I have no experience with
AArch64 and with reasonable effort I couldn't track down an architecture
manual that would clarify that. However there's a single
features/aarch64.xml register description only, that includes FP registers
unconditionally so my guess would be an FPU is implied, at least as far as
GDB is concerned at this stage.
I could be wrong though, e.g. for MIPS we have a couple of register
descriptions, all of which include FP registers, but they only cover Linux
targets where the FPU is a part of the OS ABI even where hardware has none
and software emulation is used. And bare-iron MIPS targets certainly
expose the lack of an FPU to GDB.
Anyone can confirm one way or another?
Maciej
next prev parent reply other threads:[~2014-01-15 8:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 23:04 Maciej W. Rozycki
2014-01-15 3:45 ` Joel Brobecker
2014-01-15 8:27 ` Maciej W. Rozycki [this message]
2014-01-15 8:57 ` Marcus Shawcroft
2014-01-15 9:55 ` Joel Brobecker
2014-01-15 22:22 ` Maciej W. Rozycki
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=alpine.DEB.1.10.1401150815500.6899@tp.orcam.me.uk \
--to=macro@codesourcery.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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