public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "davidm at hpl dot hp dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/18743] _init/_ lacking unwind-info
Date: Tue, 30 Nov 2004 20:24:00 -0000 [thread overview]
Message-ID: <20041130202347.19961.qmail@sourceware.org> (raw)
In-Reply-To: <20041130193704.18743.davidm@hpl.hp.com>
------- Additional Comments From davidm at hpl dot hp dot com 2004-11-30 20:23 -------
(In reply to comment #5)
> Well if _init/_fini is created by the linker then isn't this a linker bug
which should generated the unwind
> info?
I don't really care which way it goes.
When the same issue came up for ia64, we decided to deprecated .init/.fini
in favor of .init_array/.fini_array (which are much cleaner anyhow) and, from
my perspective, that choice has worked out very well.
If you search the net for "unwind info for init init_array" you'll find some old
discussions on this topic.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18743
next prev parent reply other threads:[~2004-11-30 20:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-30 19:37 [Bug target/18743] New: crtbegin/crtend " davidm at hpl dot hp dot com
2004-11-30 19:48 ` [Bug target/18743] " pinskia at gcc dot gnu dot org
2004-11-30 19:51 ` pinskia at gcc dot gnu dot org
2004-11-30 20:01 ` davidm at hpl dot hp dot com
2004-11-30 20:03 ` davidm at hpl dot hp dot com
2004-11-30 20:09 ` [Bug target/18743] _init/_ " pinskia at gcc dot gnu dot org
2004-11-30 20:24 ` davidm at hpl dot hp dot com [this message]
2004-11-30 21:15 ` [Bug target/18743] _init/_fini " schwab at suse dot de
2005-07-02 1:45 ` pinskia 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=20041130202347.19961.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).