public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "arnez at linux dot vnet.ibm.com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/63300] New: 'const volatile' sometimes stripped in debug info Date: Thu, 18 Sep 2014 16:07:00 -0000 [thread overview] Message-ID: <bug-63300-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63300 Bug ID: 63300 Summary: 'const volatile' sometimes stripped in debug info Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: debug Assignee: unassigned at gcc dot gnu.org Reporter: arnez at linux dot vnet.ibm.com With current upstream gcc, the following commands do not yield the expected output: echo 'void f (const volatile int x) { }' | gcc -xc -c -g -o foo.o - readelf -wi foo.o | grep 'volatile\|const' With an older gcc we get something like this: <1><54>: Abbrev Number: 4 (DW_TAG_const_type) <1><59>: Abbrev Number: 5 (DW_TAG_volatile_type) With the current gcc we get nothing. Indeed, the resulting debug info declares the parameter 'x' merely as an 'int' instead of 'const volatile int'. The same happens with some other combinations as well, e.g.: char *const volatile x const volatile float x const volatile int *x
next reply other threads:[~2014-09-18 16:07 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-09-18 16:07 arnez at linux dot vnet.ibm.com [this message] 2014-09-19 17:46 ` [Bug debug/63300] " mark at gcc dot gnu.org 2014-09-22 7:18 ` mark at gcc dot gnu.org 2014-09-25 7:38 ` krebbel at gcc dot gnu.org 2014-09-26 7:40 ` arnez at linux dot vnet.ibm.com 2014-09-26 7:42 ` arnez at linux dot vnet.ibm.com
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-63300-4@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).