From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: jh@suse.cz
Cc: gcc@gcc.gnu.org, gdb@sources.redhat.com
Subject: Re: Debugging of gcc 3.1 programs with -mfpmath=sse
Date: Tue, 12 Feb 2002 08:54:00 -0000 [thread overview]
Message-ID: <7458-Tue12Feb2002185243+0200-eliz@is.elta.co.il> (raw)
In-Reply-To: <20020212143841.GC5736@atrey.karlin.mff.cuni.cz> (message from Jan Hubicka on Tue, 12 Feb 2002 15:38:41 +0100)
> Date: Tue, 12 Feb 2002 15:38:41 +0100
> From: Jan Hubicka <jh@suse.cz>
>
> while hunting down the bugs in gcc3.1 SSE scalar code generation I've noticed
> that new gdb5.1 supports SSE (great :), but insist on printing the variables in
> hexadecimal form, instead of as floats, that is somewhat anoying. Since I am
> having minimal insight to gdb internals, and somehow I want to keep that for
> some time, I would like to ask, what needs to be done to get floats displayed
> right
Doesn't "p/f" work?
next prev parent reply other threads:[~2002-02-12 16:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-12 6:38 Jan Hubicka
2002-02-12 8:54 ` Eli Zaretskii [this message]
2002-02-12 8:57 ` Jan Hubicka
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=7458-Tue12Feb2002185243+0200-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=jh@suse.cz \
/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