public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/7259] GDB truncates 64 bit enums.
Date: Sat, 28 Dec 2013 03:20:00 -0000	[thread overview]
Message-ID: <bug-7259-4717-HlxmMi7KXW@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-7259-4717@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=7259

--- Comment #4 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gdb and binutils".

The branch, master has been updated
       via  0809504b5eca5e73ad721919b6b13d941ffd0a30 (commit)
      from  edef60002fc0c8d1bda6b5deb03c84d2733a32ba (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=0809504b5eca5e73ad721919b6b13d941ffd0a30

commit 0809504b5eca5e73ad721919b6b13d941ffd0a30
Author: Joel Brobecker <brobecker@adacore.com>
Date:   Mon Dec 23 11:15:42 2013 +0400

    Fix gdb.Field attributes documentation for enum types.

    The following patch ...

        | commit 14e75d8ea4fe9ed4dbf292ae4a9745e33e2ff353
        | Date:   Wed Apr 18 06:46:47 2012 +0000
        |
        |     gdb/
        |         PR symtab/7259:
        | [...]

    ... discussed under ...

        [PATCH] Allow 64-bit enum values
        http://www.sourceware.org/ml/gdb-patches/2012-03/msg00772.html

    ... introduced a change in the gdb.Fields API without documenting it:

        | I took a separate approach from the one I took in:
        |
        | http://sourceware.org/ml/gdb-patches/2012-02/msg00403.html
        |
        | and removed the overloaded meaning of the bitpos location variable to
        | fix PR symtab/7259. In the following patch, I introduce a separate
        | field_location union member 'enumval' which can accept LONGEST and
        | hence expand enum values to 64-bit signed values. With this change,
        | bitpos now only is used for (non-negative) offsets into structures,
        | since the other overload of bitpos (range bounds) were already
        | separated into struct range_bound.

    This patch updates the documentation to reflect that change.

    gdb/doc/ChangeLog:

            * gdb.texinfo (Types In Python): Fix the documentation of
            attribute "bitpos" in class gdb.Field for enum types.  Add
            documentation for attribute "enumval" in that same class.

-----------------------------------------------------------------------

Summary of changes:
 gdb/doc/ChangeLog   |    6 ++++++
 gdb/doc/gdb.texinfo |   11 +++++++----
 2 files changed, 13 insertions(+), 4 deletions(-)

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


  parent reply	other threads:[~2013-12-28  3:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-7259-4717@http.sourceware.org/bugzilla/>
2012-04-18  6:49 ` cvs-commit at gcc dot gnu.org
2012-04-18  6:52 ` cvs-commit at gcc dot gnu.org
2013-12-28  3:20 ` cvs-commit at gcc dot gnu.org [this message]
2014-06-13 19:58 ` jan.kratochvil at redhat dot com

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=bug-7259-4717-HlxmMi7KXW@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).