public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jan.kratochvil at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/53235] [4.8 Regression] 20120504 broke -fdebug-types-section
Date: Mon, 07 May 2012 14:34:00 -0000	[thread overview]
Message-ID: <bug-53235-4-ybe5EWrGta@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53235-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53235

--- Comment #2 from Jan Kratochvil <jan.kratochvil at redhat dot com> 2012-05-07 14:32:59 UTC ---
(In reply to comment #1)
> The testcase is failing because of the change from "A*" to "struct A*"?

Yes.

> Is that an important distinction?

In other cases it even crashes GDB, originally filed as:
  http://sourceware.org/bugzilla/show_bug.cgi?id=14060
Or I see
  Internal error: non-aggregate type to value_struct_elt_for_reference
  Function "policy1::function" not defined.
  etc.

> If so, could you handle the case of a nameless typedef specially on your end?

Yes; I wanted to know first if this is an intended change.

FYI it does not seem to be DWARF compliant:
  The typedef entry has a DW_AT_name attribute whose value is a null-terminated
  string containing the name of the typedef as it appears in the source
program.


  parent reply	other threads:[~2012-05-07 14:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-04 18:30 [Bug debug/53235] New: " jan.kratochvil at redhat dot com
2012-05-07  9:48 ` [Bug debug/53235] " rguenth at gcc dot gnu.org
2012-05-07 14:25 ` jason at gcc dot gnu.org
2012-05-07 14:34 ` jan.kratochvil at redhat dot com [this message]
2012-05-07 14:53 ` jason at gcc dot gnu.org
2012-05-07 15:12 ` jan.kratochvil at redhat dot com
2012-05-13  5:12 ` jason at gcc dot gnu.org
2012-05-14  2:24 ` jason at gcc dot gnu.org
2012-05-19 14:30 ` jan.kratochvil at redhat dot com
2012-05-24  5:49 ` jan.kratochvil at redhat dot com
2012-07-07 14:13 ` jason at gcc dot gnu.org
2012-07-17 19:10 ` jan.kratochvil at redhat dot com
2012-07-19  3:17 ` jason at gcc dot gnu.org
2012-07-19 20:02 ` jason at gcc dot gnu.org
2012-07-19 20:09 ` jason at gcc dot gnu.org
2012-09-06  3:34 ` ccoutant at gcc dot gnu.org
2013-01-20 20:36 ` mrs 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-53235-4-ybe5EWrGta@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).