public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "krisztian.kocsis at optimaster dot eu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/51255] Using -fwhole-program breaks code which puts values in .ctors or .init_array
Date: Mon, 16 Apr 2012 14:37:00 -0000	[thread overview]
Message-ID: <bug-51255-4-lpaElp1xIz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51255-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Krisztian Kocsis <krisztian.kocsis at optimaster dot eu> 2012-04-16 14:35:37 UTC ---
I currently know that glibc uses it but don't know who else use it.
In my projects I always use constructor/destructor attributes because with them
I can control the exection order.


  parent reply	other threads:[~2012-04-16 14:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-21  5:06 [Bug lto/51255] New: Using -flto " ian at airs dot com
2012-03-05 18:41 ` [Bug lto/51255] " pinskia at gcc dot gnu.org
2012-03-06 10:26 ` [Bug middle-end/51255] Using -fwhole-program " rguenth at gcc dot gnu.org
2012-03-19 15:52 ` hubicka at gcc dot gnu.org
2012-04-16 12:07 ` krisztian.kocsis at optimaster dot eu
2012-04-16 13:51 ` hubicka at ucw dot cz
2012-04-16 14:37 ` krisztian.kocsis at optimaster dot eu [this message]
2013-06-20  3:44 ` carlos at redhat dot com
2013-06-20  6:56 ` krisztian.kocsis at optimaster dot eu
2021-12-11 18:59 ` pinskia 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-51255-4-lpaElp1xIz@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).