public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/104238] dwarf DW_AT_const_value causes overflow in readelf Date: Wed, 26 Jan 2022 13:43:48 +0000 [thread overview] Message-ID: <bug-104238-4-iCwgkWrm4P@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104238-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104238 Martin Liška <marxin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2022-01-26 Status|UNCONFIRMED |WAITING Ever confirmed|0 |1 --- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> --- Can't see it with: readelf -v GNU readelf (GNU Binutils; openSUSE Tumbleweed) 2.37.20211112-3 $ gcc-11 pr104238.c -c -g -O1 && readelf --debug-dump=info,abbrev pr104238.o Contents of the .debug_info section: ... <2><4c>: Abbrev Number: 3 (DW_TAG_variable) <4d> DW_AT_name : var <51> DW_AT_decl_file : 1 <52> DW_AT_decl_line : 2 <53> DW_AT_decl_column : 22 <54> DW_AT_type : <0x63> <58> DW_AT_const_value : -9223372036854775808 <2><62>: Abbrev Number: 0 ...
next prev parent reply other threads:[~2022-01-26 13:43 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-26 10:40 [Bug debug/104238] New: " tbuyukliev at vmware dot com 2022-01-26 11:41 ` [Bug debug/104238] " jakub at gcc dot gnu.org 2022-01-26 13:11 ` rguenth at gcc dot gnu.org 2022-01-26 13:43 ` marxin at gcc dot gnu.org [this message] 2022-01-26 16:49 ` tbuyukliev at vmware dot com 2022-01-26 19:14 ` jakub at gcc dot gnu.org 2022-01-26 19:30 ` 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-104238-4-iCwgkWrm4P@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).