public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wilson at specifixinc dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/14813] [3.4/3.5 Regression] The wrong init order
Date: Wed, 21 Apr 2004 23:19:00 -0000	[thread overview]
Message-ID: <20040421223803.4654.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040401195835.14813.hjl@lucon.org>


------- 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


  parent reply	other threads:[~2004-04-21 22:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-01 19:58 [Bug target/14813] New: " hjl at lucon dot org
2004-04-01 20:00 ` [Bug target/14813] " hjl at lucon dot org
2004-04-01 20:03 ` [Bug target/14813] [3.4.0 Regression] " hjl at lucon dot org
2004-04-01 20:05 ` [Bug target/14813] [3.4/3.5 " pinskia at gcc dot gnu dot org
2004-04-01 21:05 ` hjl at lucon dot org
2004-04-06  9:42 ` jakub at gcc dot gnu dot org
2004-04-06 18:09 ` hjl at lucon dot org
2004-04-13  0:03 ` hjl at lucon dot org
2004-04-13 18:35 ` hjl at lucon dot org
2004-04-13 18:36 ` pinskia at gcc dot gnu dot org
2004-04-21 23:19 ` wilson at specifixinc dot com [this message]
2004-04-21 23:42 ` cvs-commit at gcc dot gnu dot org
2004-04-22  0:06 ` 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=20040421223803.4654.qmail@sources.redhat.com \
    --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).