[patch] Fix new FAIL `reject p 0x1.1' [fixup]

[Jan Kratochvil]

On Mon, 23 Aug 2010 17:35:07 +0200, Doug Evans wrote:
> On Fri, Aug 20, 2010 at 4:58 AM, Joseph S. Myers <joseph@codesourcery.com> wrote:
> > On Fri, 20 Aug 2010, Jan Kratochvil wrote:
> >> On Fri, 20 Aug 2010 09:34:30 +0200, Jan Kratochvil wrote:
> >> 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?
> 
> I don't know what gdb is intended to accept.

So far I believe GDB is intended to be more relaxed than the C compiler.
(PR symtab/11846 -> is accepted interchangeable with .)
(static symbols get resolved from not-current CUs)
etc.

While thanks for catching it I still believe now my testcase update is the
appropriate fix - if glibc supports then extended input syntax let the GDB
user benefit from it.


Thanks,
Jan