From: Jason Merrill <jason@redhat.com>
To: Jan Hubicka <hubicka@ucw.cz>
Cc: Jakub Jelinek <jakub@redhat.com>, Ilya Verbin <iverbin@gmail.com>,
gcc-patches@gcc.gnu.org, rguenther@suse.de
Subject: Re: Silence merge warnings on artificial types
Date: Tue, 31 Mar 2015 13:26:00 -0000 [thread overview]
Message-ID: <551AA088.8080803@redhat.com> (raw)
In-Reply-To: <20150331075121.GB62830@kam.mff.cuni.cz>
On 03/31/2015 03:51 AM, Jan Hubicka wrote:
> Jason, please do you know what is meaning of DECL_ARTIFICIAL on class type
> names? Perhaps we can drop them to 0 in free lang data?
It indicates the implicit typedef that let's you say 'S' instead of
'struct S' without writing 'typedef struct S S' yourself.
dwarf2out.c uses this information in TYPE_DECL_IS_STUB and
is_redundant_typedef, so we can't clear it until after debug info
generation.
Jason
next prev parent reply other threads:[~2015-03-31 13:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 3:03 Silence merge warnings on artiical types Jan Hubicka
2015-03-30 8:30 ` Richard Biener
2015-03-30 8:48 ` Jan Hubicka
2015-03-30 15:36 ` Ilya Verbin
2015-03-30 17:06 ` Jan Hubicka
2015-03-30 17:11 ` Ilya Verbin
2015-03-30 17:16 ` Jan Hubicka
2015-03-30 17:21 ` Jakub Jelinek
2015-03-30 17:23 ` Jan Hubicka
2015-03-30 17:53 ` Jason Merrill
2015-03-31 7:51 ` Silence merge warnings on artificial types Jan Hubicka
2015-03-31 13:26 ` Jason Merrill [this message]
2015-04-02 18:23 ` Ilya Verbin
2015-04-02 18:37 ` Jan Hubicka
2015-04-02 19:06 ` Jakub Jelinek
2015-04-03 13:36 ` Jakub Jelinek
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=551AA088.8080803@redhat.com \
--to=jason@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=iverbin@gmail.com \
--cc=jakub@redhat.com \
--cc=rguenther@suse.de \
/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).