public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pluto at agmk dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/54671] [4.7/4.8 Regression] gcc 4.7.2 -Wl,--no-ctors-in-init-array causes binutils test failure, works with 4.7.1
Date: Tue, 25 Sep 2012 19:23:00 -0000 [thread overview]
Message-ID: <bug-54671-4-bY0SJmX4vw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54671-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54671
--- Comment #4 from Pawel Sikora <pluto at agmk dot net> 2012-09-25 19:23:15 UTC ---
(In reply to comment #2)
> I think this is a user bug. If gcc is configured against binutils that support
> conversion of ctors into init_array, then it will assume it, obviously you
> can't use --no-ctors-in-init-array then, you'd need to configure gcc not to
> assume it.
> Why do you need to use that option (actually, I wonder why the linker has that
> option at all)?
e.g. i'd like to build an application for an old enterprise distro
(which doesn't support init/fini arrays) on my brand new distro.
-Wl,--no-ctors-in-init-array works perfectly fine in this case.
next prev parent reply other threads:[~2012-09-25 19:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-22 18:59 [Bug other/54671] New: " ncahill_alt at yahoo dot com
2012-09-22 19:00 ` [Bug other/54671] " ncahill_alt at yahoo dot com
2012-09-24 9:29 ` [Bug other/54671] [4.7/4.8 Regression] " rguenth at gcc dot gnu.org
2012-09-24 10:14 ` jakub at gcc dot gnu.org
2012-09-24 20:14 ` ncahill_alt at yahoo dot com
2012-09-25 19:23 ` pluto at agmk dot net [this message]
2012-11-07 18:16 ` jakub 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-54671-4-bY0SJmX4vw@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).