public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/45388] [4.6 Regression] Global constructor not found
Date: Sun, 12 Dec 2010 19:55:00 -0000	[thread overview]
Message-ID: <bug-45388-4-M0VcALPawS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-45388-4@http.gcc.gnu.org/bugzilla/>

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

Jan Hubicka <hubicka at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED

--- Comment #8 from Jan Hubicka <hubicka at gcc dot gnu.org> 2010-12-12 19:54:28 UTC ---
Mine, patch sent http://gcc.gnu.org/ml/gcc-patches/2010-12/msg00961.html

Sorry about the delay. 

The problem is not that I would not want constructors to be global. The problem
was that since the original constructor merging was introduced (in 2004), C++
FE produced collect2 recognizable names for no reason. This problem was masked
by fact that the code set always inline flag on all functions. This is wrong,
since not all functions are inlinable so it can lead to ICE when non-inlinable
static constructor is introduced.

The patch should avoid those recognizable names until final merging pass and
thus avoid the problem.

Honza


  parent reply	other threads:[~2010-12-12 19:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-45388-4@http.gcc.gnu.org/bugzilla/>
2010-09-24 21:09 ` sje at cup dot hp.com
2010-09-24 22:40 ` sje at cup dot hp.com
2010-09-25  0:15 ` sje at cup dot hp.com
2010-09-27 10:39 ` dave at hiauly1 dot hia.nrc.ca
2010-12-12 19:55 ` hubicka at gcc dot gnu.org [this message]
2010-12-13 17:29 ` hubicka at gcc dot gnu.org
2010-12-13 17:32 ` hubicka at gcc dot gnu.org
2010-12-13 18:05 ` amonakov at gcc dot gnu.org
2010-12-14  1:27 ` hubicka at gcc dot gnu.org
2010-12-15 11:55 ` jakub at gcc dot gnu.org
2010-08-23 20:51 [Bug middle-end/45388] New: " danglin at gcc dot gnu dot org
2010-08-23 20:58 ` [Bug middle-end/45388] " danglin at gcc dot gnu dot org
2010-08-24  8:55 ` rguenth at gcc dot gnu dot org
2010-08-24 12:13 ` hubicka at gcc dot gnu dot org
2010-08-24 15:07 ` dave at hiauly1 dot hia dot nrc dot ca
2010-09-02 11:19 ` rguenth 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=bug-45388-4-M0VcALPawS@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).