public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "dje at google dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/14148] -fdebug-types-section regresses ststic scope of types
Date: Thu, 24 May 2012 00:16:00 -0000 [thread overview]
Message-ID: <bug-14148-4717-VUrnJ1kiMi@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14148-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=14148
dje at google dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ccoutant at google dot com,
| |dje at google dot com
--- Comment #1 from dje at google dot com 2012-05-24 00:15:47 UTC ---
Cary told me that Jason is changing gcc to always create a skeleton type in the
CU with the DW_FORM_ref_sig8 living in the skeleton entry.
It's a space saving optimization.
Whether we need to care about producers that don't do this, I'm not sure.
Expanding scan_partial_symbols to watch for type unit references feels
problematic.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2012-05-24 0:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 21:13 [Bug symtab/14148] New: " jan.kratochvil at redhat dot com
2012-05-24 0:16 ` dje at google dot com [this message]
2012-05-24 2:18 ` [Bug symtab/14148] -fdebug-types-section regresses static " jan.kratochvil at redhat dot com
2012-05-24 4:35 ` dje at google dot com
2020-04-13 21:33 ` vries at gcc dot gnu.org
2020-04-17 13:39 ` vries at gcc dot gnu.org
2020-04-25 15:13 ` vries at gcc dot gnu.org
2020-04-25 15:19 ` cvs-commit at gcc dot gnu.org
2020-04-29 11:23 ` vries 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-14148-4717-VUrnJ1kiMi@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.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).