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 debug/113977] debug info for alignment of structure is unspecified
Date: Sun, 18 Feb 2024 02:29:26 +0000 [thread overview]
Message-ID: <bug-113977-4-3DvAqOFmf5@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 #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
This seems like a bug in gdb really.
GCC produces:
```
.uleb128 0x3 # (DIE (0x2e) DW_TAG_structure_type)
.ascii "s7\0" # DW_AT_name
.byte 0x7 # DW_AT_byte_size
# DW_AT_decl_file (1, /app/example.cpp)
.byte 0x1 # DW_AT_decl_line
# DW_AT_decl_column (0x8)
.long 0x41 # DW_AT_sibling
.uleb128 0x4 # (DIE (0x38) DW_TAG_member)
.ascii "_\0" # DW_AT_name
# DW_AT_decl_file (1, /app/example.cpp)
.byte 0x1 # DW_AT_decl_line
# DW_AT_decl_column (0x12)
.long 0x41 # DW_AT_type
# DW_AT_data_member_location (0)
.byte 0 # end of children of DIE 0x2e
.uleb128 0x2 # (DIE (0x41) DW_TAG_array_type)
.long 0x58 # DW_AT_type
.long 0x51 # DW_AT_sibling
```
```
.ascii "x\0" # DW_AT_name
# DW_AT_decl_file (1, /app/example.cpp)
.byte 0x7 # DW_AT_decl_line
# DW_AT_decl_column (0xd)
.long 0xf1 # DW_AT_type
.uleb128 0x2 # DW_AT_location
.byte 0x91 # DW_OP_fbreg
.sleb128 -30
```
```
.uleb128 0x2 # (DIE (0xf1) DW_TAG_array_type)
.long 0x2e # DW_AT_type
.long 0x101 # DW_AT_sibling
.uleb128 0x1 # (DIE (0xfa) DW_TAG_subrange_type)
.long 0x51 # DW_AT_type
.byte 0x1 # DW_AT_upper_bound
.byte 0 # end of children of DIE 0xf1
```
next prev parent reply other threads:[~2024-02-18 2:29 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 ` pinskia at gcc dot gnu.org [this message]
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
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-3DvAqOFmf5@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).