From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Doug Evans <dje@google.com>, Andreas Schwab <schwab@redhat.com>,
gdb-patches@sourceware.org
Subject: Re: [patch] Fix new FAIL `reject p 0x1.1' [fixup] [Re: [patch] Handle 0 result from sscanf when parsing fp values.]
Date: Fri, 20 Aug 2010 11:58:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1008201152480.2209@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20100820073703.GA19257@host1.dyn.jankratochvil.net>
On Fri, 20 Aug 2010, Jan Kratochvil wrote:
> [fixup]
>
> On Fri, 20 Aug 2010 09:34:30 +0200, Jan Kratochvil wrote:
> Hi,
>
> 0x1.1 is a perfectly valid hexadecimal floating point. The new testcase:
It's not valid in C source code (a binary exponent is required), though it
is valid as input to strtod (like INF, NAN, NAN(n-char-sequence_opt) etc.)
- is the intention here that GDB deliberately accepts something beyond
what would be valid in C source code?
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2010-08-20 11:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-17 0:31 [patch] Handle 0 result from sscanf when parsing fp values Doug Evans
2010-08-17 8:18 ` Andreas Schwab
2010-08-17 11:37 ` Doug Evans
2010-08-18 20:38 ` Doug Evans
2010-08-20 7:34 ` [patch] Fix new FAIL `reject p 0x1.1' [Re: [patch] Handle 0 result from sscanf when parsing fp values.] Jan Kratochvil
2010-08-20 7:37 ` [patch] Fix new FAIL `reject p 0x1.1' [fixup] " Jan Kratochvil
2010-08-20 11:58 ` Joseph S. Myers [this message]
2010-08-23 15:35 ` Doug Evans
2010-08-23 18:55 ` [patch] Fix new FAIL `reject p 0x1.1' [fixup] Jan Kratochvil
2010-08-23 19:49 ` Doug Evans
2010-08-23 19:57 ` Doug Evans
2010-08-31 19:38 ` Jan Kratochvil
2010-08-31 22:51 ` Doug Evans
2010-09-02 15:11 ` Jan Kratochvil
2010-09-06 22:29 ` Jan Kratochvil
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=Pine.LNX.4.64.1008201152480.2209@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=schwab@redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).