public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/30297] [4.1/4.2/4.3 regression] ICE with extern "C" and inheritance
Date: Wed, 27 Dec 2006 04:02:00 -0000	[thread overview]
Message-ID: <20061227040152.11168.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30297-1771@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from pinskia at gcc dot gnu dot org  2006-12-27 04:01 -------
And another one:
Index: tree.c
===================================================================
--- tree.c      (revision 120211)
+++ tree.c      (working copy)
@@ -2199,6 +2199,10 @@
      then handles a few special cases.  Ideally, we would calculate
      linkage first, and then transform that into a concrete
      implementation.  */
+     
+  /* Field decls have no linkage.  */
+  if (TREE_CODE (decl) == FIELD_DECL)
+    return lk_none;

   /* Things that don't have names have no linkage.  */
   if (!DECL_NAME (decl))


-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|unassigned at gcc dot gnu   |pinskia at gcc dot gnu dot
                   |dot org                     |org
             Status|NEW                         |ASSIGNED
   Last reconfirmed|2006-12-26 22:32:09         |2006-12-27 04:01:52
               date|                            |


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


  parent reply	other threads:[~2006-12-27  4:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-26 11:20 [Bug c++/30297] New: " reichelt at gcc dot gnu dot org
2006-12-26 11:21 ` [Bug c++/30297] " reichelt at gcc dot gnu dot org
2006-12-26 22:32 ` pinskia at gcc dot gnu dot org
2006-12-27  4:02 ` pinskia at gcc dot gnu dot org [this message]
2007-01-10 21:29 ` pinskia at gcc dot gnu dot org
2007-01-25  6:07 ` mmitchel at gcc dot gnu dot org
2007-02-14  9:19 ` mmitchel at gcc dot gnu dot org
2007-05-27 19:40 ` pinskia at gcc dot gnu dot org
2007-11-05 20:55 ` tromey at gcc dot gnu dot org
2007-11-05 22:23 ` pinskia at gcc dot gnu dot org
2007-11-08 19:51 ` tromey at gcc dot gnu dot org
2007-11-08 19:51 ` [Bug c++/30297] [4.1/4.2 " tromey at gcc dot gnu dot org
2007-11-10  3:55 ` patchapp at dberlin dot org
2007-11-10  4:00 ` patchapp at dberlin dot org
2007-11-10  4:06 ` patchapp at dberlin dot org
2008-07-04 21:47 ` [Bug c++/30297] [4.2 " jsm28 at gcc dot gnu dot org
2009-03-30 20:19 ` jsm28 at gcc dot gnu dot 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=20061227040152.11168.qmail@sourceware.org \
    --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).