public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "matz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/47946] Dwarf uses 64-bits to refer to a structure offset unnecessarily
Date: Tue, 01 Mar 2011 17:07:00 -0000 [thread overview]
Message-ID: <bug-47946-4-tRfNuLscH7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47946-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47946
Michael Matz <matz at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |matz at gcc dot gnu.org
--- Comment #2 from Michael Matz <matz at gcc dot gnu.org> 2011-03-01 17:06:42 UTC ---
Due to the definition of dwarf2/3 these offsets are negative on little-endian
machines. This was fixed in dwarf4, see
http://dwarfstd.org/ShowIssue.php?issue=081130.1&type=closed3
GCC doesn't yet support this part of dwarf4. But even for dwarf2 we could
emit this signed number as sleb128, not as unsigned number (that is what
causes us to use FORM_data8).
next prev parent reply other threads:[~2011-03-01 17:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 15:31 [Bug debug/47946] New: " hariharans at picochip dot com
2011-03-01 15:31 ` [Bug debug/47946] " hariharans at picochip dot com
2011-03-01 17:07 ` matz at gcc dot gnu.org [this message]
2011-03-01 18:39 ` jakub at gcc dot gnu.org
2011-03-02 10:11 ` hariharans at picochip dot com
2011-03-14 20:07 ` jakub at gcc dot gnu.org
2011-03-14 20:13 ` jakub at gcc dot gnu.org
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-47946-4-tRfNuLscH7@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).