public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/46796] debug info missing builtin type names with lto
Date: Tue, 07 Dec 2010 16:33:00 -0000	[thread overview]
Message-ID: <bug-46796-4-HRJlD4WQeb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46796-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from rguenther at suse dot de <rguenther at suse dot de> 2010-12-07 16:32:57 UTC ---
On Tue, 7 Dec 2010, mrs at gcc dot gnu.org wrote:

> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46796
> 
> --- Comment #7 from mrs at gcc dot gnu.org <mrs at gcc dot gnu.org> 2010-12-07 16:17:09 UTC ---
> Ok, I can confirm that ptype i is better, now, the next problem:
> 
> (gdb) ptype a1
> type = volatile __unknown__
> 
> :-(

Yeah, I saw that but didn't yet debug why it happens.


  parent reply	other threads:[~2010-12-07 16:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-03 23:33 [Bug lto/46796] New: debug info missing builtin type names on darwin mrs at gcc dot gnu.org
2010-12-03 23:42 ` [Bug lto/46796] " rguenth at gcc dot gnu.org
2010-12-03 23:45 ` mrs at gcc dot gnu.org
2010-12-03 23:51 ` [Bug debug/46796] debug info missing builtin type names with lto rguenth at gcc dot gnu.org
2010-12-03 23:53 ` rguenth at gcc dot gnu.org
2010-12-06 10:08 ` rguenth at gcc dot gnu.org
2010-12-06 10:10 ` rguenth at gcc dot gnu.org
2010-12-07 16:17 ` mrs at gcc dot gnu.org
2010-12-07 16:33 ` rguenther at suse dot de [this message]
2010-12-10 14:33 ` rguenth at gcc dot gnu.org
2011-12-20  9:50 ` rguenth at gcc dot gnu.org
2011-12-20 10:21 ` rguenth 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-46796-4-HRJlD4WQeb@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).