public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aldyh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/66668] [6 regression] FAIL: gcc.dg/debug/dwarf2/stacked-qualified-types-3.c scan-assembler-times DIE \\([^\n]*\\) DW_TAG_(?:const|volatile|atomic|restrict)_type 8
Date: Wed, 01 Jul 2015 17:14:00 -0000	[thread overview]
Message-ID: <bug-66668-4-9PWmXVS0wH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66668-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66668

--- Comment #2 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
Yes, this is a known issue, likely across all architectures.  I mentioned this
upon merge of the debug-early work:

https://gcc.gnu.org/ml/gcc/2015-06/msg00093.html

As I discussed in the above post, this is a missed optimization while merging
the common denominator of a set of qualifiers for a type within a DIE. For
example, if two types share "const volatile" (say "const volatile int" and
"const volatile char"), dwarf2out outputs things in the most efficient manner
as to share the maximum common type DIEs. This is not working, as
TYPE_MAIN_VARIANTs are not complete by the time early dwarf is run.

Thanks for opening the PR.


  parent reply	other threads:[~2015-07-01 17:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-25 14:10 [Bug debug/66668] New: " danglin at gcc dot gnu.org
2015-07-01 13:58 ` [Bug debug/66668] [6 regression] " ro at gcc dot gnu.org
2015-07-01 17:14 ` aldyh at gcc dot gnu.org [this message]
2021-02-23  3:09 ` hp at gcc dot gnu.org
2021-03-05  1:01 ` cvs-commit at gcc dot gnu.org
2021-03-05  1:10 ` hp at gcc dot gnu.org
2022-01-09  0:54 ` [Bug debug/66668] " 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-66668-4-9PWmXVS0wH@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).