public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia 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: Sun, 18 Feb 2024 02:47:32 +0000 [thread overview]
Message-ID: <bug-113977-4-Px1vTn0XuT@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
--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Tan Senqi from comment #4)
> (In reply to Andrew Pinski from comment #3)
> I think gcc can generate a DW_AT_alignment for my struct to solve this
> problem. But why the alignment is considered as 8, I am not sure about this.
> If it is inherited from the default structure alignment requirement on the
> platform, then gcc should specify alignment for those whose alignment is not
> 8. Or 8 is not the default value by DWARF5(i.e. undefined), then it is
> surely a bug in gdb.
So reading the definition of DW_AT_alignment, it is if the alignment is not the
default for that type. In this case it should be 1 as char arrays have
alignment of 1 inside structs.
See https://dwarfstd.org/issues/140528.1.html for the definition.
in this case the ABI specifies the alignment and GCC does not need to emit
DW_AT_alignment since it is not different from the ABI. This would mean the bug
is in gdb's gcc_convert_symbol, eg.:
```
gcc_convert_symbol "z": local symbol
gdb command line:1:1: error: size of array element is not a multiple of its
alignment
```
I am testing the trunk gdb right now to see if it was fixed.
next prev parent reply other threads:[~2024-02-18 2:47 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 [this message]
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
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-Px1vTn0XuT@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).