From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4663 invoked by alias); 21 Apr 2004 22:38:05 -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 4655 invoked by alias); 21 Apr 2004 22:38:03 -0000 Date: Wed, 21 Apr 2004 23:19:00 -0000 Message-ID: <20040421223803.4654.qmail@sources.redhat.com> From: "wilson at specifixinc dot com" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20040401195835.14813.hjl@lucon.org> References: <20040401195835.14813.hjl@lucon.org> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug target/14813] [3.4/3.5 Regression] The wrong init order X-Bugzilla-Reason: CC X-SW-Source: 2004-04/txt/msg01934.txt.bz2 List-Id: ------- Additional Comments From wilson at specifixinc dot com 2004-04-21 22:37 ------- Subject: Re: [3.4/3.5 Regression] The wrong init order pinskia at gcc dot gnu dot org wrote: > ------- Additional Comments From pinskia at gcc dot gnu dot org 2004-04-01 20:05 ------- > The last change to crtend.asm was over a year ago why was this not found way before the release? This only fails if an application or library uses init_array/fini_array. GCC still uses ctors/dtors sections instead of the preferred and standardized init_array/fini_array sections. So the only way that you can trigger this problem is if someone explicitly uses attribute section init_array, or if you link with code compiled by another compiler. I suspect the latter method is how HJ found the problem, e.g. he may have noticed the problem after trying to link icc compiled code with gcc compiled code. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14813