public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libcc1/113977] debug info for alignment of structure is unspecified
Date: Tue, 20 Feb 2024 18:27:06 +0000	[thread overview]
Message-ID: <bug-113977-4-9BCyBy4Ck8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113977-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113977

Tom Tromey <tromey at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at gcc dot gnu.org

--- Comment #9 from Tom Tromey <tromey at gcc dot gnu.org> ---
I think this should be reopened -- some of the fix has
to happen in libcc1.

When this code was written, there was no way to find
the alignment in DWARF.  That's since been fixed but
the protocol wasn't updated.  There are some comments
about this, see libcc1/libcc1plugin.cc:

      // FIXME there's no way to get this from DWARF,
      // or even, it seems, a particularly good way to deduce it.
      SET_TYPE_ALIGN (record_or_union_type,
                      TYPE_PRECISION (pointer_sized_int_node));

  parent reply	other threads:[~2024-02-20 18:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-18  2:06 [Bug debug/113977] New: " tsqurt at outlook dot com
2024-02-18  2:29 ` [Bug debug/113977] " pinskia at gcc dot gnu.org
2024-02-18  2:32 ` [Bug libcc1/113977] " pinskia at gcc dot gnu.org
2024-02-18  2:35 ` pinskia at gcc dot gnu.org
2024-02-18  2:41 ` tsqurt at outlook dot com
2024-02-18  2:47 ` pinskia at gcc dot gnu.org
2024-02-18  2:48 ` pinskia at gcc dot gnu.org
2024-02-18  2:58 ` pinskia at gcc dot gnu.org
2024-02-18  3:06 ` pinskia at gcc dot gnu.org
2024-02-20 18:27 ` tromey at gcc dot gnu.org [this message]
2024-02-20 18:32 ` pinskia at gcc dot gnu.org
2024-02-22  1:46 ` tromey at gcc dot gnu.org
2024-02-29 16:08 ` cvs-commit at gcc dot gnu.org
2024-02-29 16:34 ` tromey at gcc dot gnu.org
2024-03-07  8:20 ` pinskia 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-113977-4-9BCyBy4Ck8@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).