[Bug gdb/18318] Printing an hexadecimal floating constant with negative exponent gives wrong result

["cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=18318

--- Comment #4 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom Tromey <tromey@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=2b4e6a3f4b66284556254f548716c7b21b93524a

commit 2b4e6a3f4b66284556254f548716c7b21b93524a
Author: Tom Tromey <tom@tromey.com>
Date:   Thu Jun 11 10:34:31 2020 -0600

    Fix hex floating point lexing

    PR gdb/18318 notes that gdb will sometimes incorrectly handle hex
    floating point input.  This turns out to be a bug in the C lexer; the
    'p' was not being correctly recognized, and so the exponent was not
    always passed to the floating point "from_string" method.

    Tested by the buildbot "Fedora-x86_64-m64" builder.

    gdb/ChangeLog
    2020-06-11  Tom Tromey  <tom@tromey.com>

            PR gdb/18318:
            * c-exp.y (lex_one_token): Handle 'p' like 'e'.

    gdb/testsuite/ChangeLog
    2020-06-11  Tom Tromey  <tom@tromey.com>

            PR gdb/18318:
            * gdb.base/printcmds.exp (test_float_accepted): Add more hex
            floating point tests.

-- 
You are receiving this mail because:
You are on the CC list for the bug.