public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "puetzk at puetzk dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/78100] DWARF symbols for an array sometimes missing the array length Date: Sat, 01 Jun 2024 13:33:37 +0000 [thread overview] Message-ID: <bug-78100-4-ACwoOsGaDS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-78100-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78100 --- Comment #10 from Kevin Puetz <puetzk at puetzk dot org> --- The godbolt recipe also nails down the other end of the version range - 5.4 produced something weirder still (a single DW_TAG_variable with DW_AT_external=true, but also with DW_AT_location and DW_AT_upper_bound present - so it kind of mushed the two decls together with all the attributes of both). 6.1 starts emitting two separate DW_TAG_variable DIEs, one with DW_AT_external=true and the other with DW_AT_location, using DW_AT_specification to link them; but it lost the DW_AT_upper_bound. Then 10.1...trunk all seem fixed, emitting an incomplete `extern` and a complete definition, as it should. So "Known to fail" should be 6.1-9.5, "Known to Work" should be 10.0+ (and bug 91507 can also be marked "RESOLVED FIXED" since 10.1 is long since released). I'd update the metadata myself but don't the permission bits...
prev parent reply other threads:[~2024-06-01 13:33 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-78100-4@http.gcc.gnu.org/bugzilla/> 2024-01-05 17:56 ` gccbugs at dima dot secretsauce.net 2024-03-14 16:38 ` cJ-gcc at zougloub dot eu 2024-06-01 3:38 ` puetzk at puetzk dot org 2024-06-01 3:56 ` puetzk at puetzk dot org 2024-06-01 4:01 ` puetzk at puetzk dot org 2024-06-01 11:52 ` mark at gcc dot gnu.org 2024-06-01 13:33 ` puetzk at puetzk dot org [this message]
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-78100-4-ACwoOsGaDS@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: linkBe 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).