From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20568 invoked by alias); 30 Nov 2004 20:24:07 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 19962 invoked by uid 48); 30 Nov 2004 20:23:47 -0000 Date: Tue, 30 Nov 2004 20:24:00 -0000 Message-ID: <20041130202347.19961.qmail@sourceware.org> From: "davidm at hpl dot hp dot com" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20041130193704.18743.davidm@hpl.hp.com> References: <20041130193704.18743.davidm@hpl.hp.com> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug target/18743] _init/_ lacking unwind-info X-Bugzilla-Reason: CC X-SW-Source: 2004-11/txt/msg03857.txt.bz2 List-Id: ------- 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