From: Eric Botcazou <ebotcazou@adacore.com>
To: gcc-patches@gcc.gnu.org
Subject: [patch] Extend TYPE_DECL_IS_STUB trick in dwarf2out.c
Date: Sat, 09 Apr 2011 11:38:00 -0000 [thread overview]
Message-ID: <201104091332.50754.ebotcazou@adacore.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 346 bytes --]
As explained in http://gcc.gnu.org/ml/gcc/2011-04/msg00167.html, this patch
extends the TYPE_DECL_IS_STUB trick in dwarf2out.c to all types.
Tested on x86_64-suse-linux (GCC + GDB), OK for the mainline?
2011-04-09 Eric Botcazou <ebotcazou@adacore.com>
* dwarf2out.c (TYPE_DECL_IS_STUB): Extend mechanism to all types.
--
Eric Botcazou
[-- Attachment #2: p.diff --]
[-- Type: text/x-diff, Size: 1444 bytes --]
Index: dwarf2out.c
===================================================================
--- dwarf2out.c (revision 172201)
+++ dwarf2out.c (working copy)
@@ -6003,19 +6003,19 @@ skeleton_chain_node;
#endif
/* Define a macro which returns nonzero for a TYPE_DECL which was
- implicitly generated for a tagged type.
+ implicitly generated for a type.
- Note that unlike the gcc front end (which generates a NULL named
- TYPE_DECL node for each complete tagged type, each array type, and
- each function type node created) the g++ front end generates a
- _named_ TYPE_DECL node for each tagged type node created.
+ Note that, unlike the C front-end (which generates a NULL named
+ TYPE_DECL node for each complete tagged type, each array type,
+ and each function type node created) the C++ front-end generates
+ a _named_ TYPE_DECL node for each tagged type node created.
These TYPE_DECLs have DECL_ARTIFICIAL set, so we know not to
- generate a DW_TAG_typedef DIE for them. */
+ generate a DW_TAG_typedef DIE for them. Likewise with the Ada
+ front-end, but for each type, tagged or not. */
#define TYPE_DECL_IS_STUB(decl) \
(DECL_NAME (decl) == NULL_TREE \
|| (DECL_ARTIFICIAL (decl) \
- && is_tagged_type (TREE_TYPE (decl)) \
&& ((decl == TYPE_STUB_DECL (TREE_TYPE (decl))) \
/* This is necessary for stub decls that \
appear in nested inline functions. */ \
reply other threads:[~2011-04-09 11:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201104091332.50754.ebotcazou@adacore.com \
--to=ebotcazou@adacore.com \
--cc=gcc-patches@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).