public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: Jakub Jelinek <jakub@redhat.com>,
	David Edelsohn <dje.gcc@gmail.com>,
		GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: PING: PATCH: PR target/46770: Use .init_array/.fini_array sections
Date: Mon, 22 Aug 2011 20:50:00 -0000	[thread overview]
Message-ID: <CAMe9rOpeQrSh_N4ELYnsme+ZvW7X1G1aK2q0F64=gx15eXeByw@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1108221858090.31559@digraph.polyomino.org.uk>

On Mon, Aug 22, 2011 at 11:59 AM, Joseph S. Myers
<joseph@codesourcery.com> wrote:
> On Mon, 22 Aug 2011, H.J. Lu wrote:
>
>> > Require a good assembler on ELF targets and just enable this by default
>> > for them without trying a configure test that won't work for cross
>> > compilation (AC_RUN_IFELSE is bad).
>> >
>> > The toplevel config/elf.m4 provides a good notion of what is or is not
>> > ELF (if there are problems, we can fix that file).  Only a handful of
>> > targets support non-GNU assemblers; for the vast bulk of targets we should
>> > assume a not-too-old GNU assembler.  That way, the configure test can be
>> > used to cause a configure-time error if the assembler is defective and it
>> > doesn't matter that the test is late.
>> >
>>
>> A working .init_array support needs assembler, linker and libc.
>> That is why AC_RUN_IFELSE is used.
>
> A working .init_array is a standard part of ELF.  The correct default for
> cross compilation to an ELF target (as determined by elf.m4) is to assume
> it is present; this is not a matter of a GNU extension that could affect
> interoperation with other tools.
>

I wish we can make  .init_array support mandatory.  One problem is
to support mixing input .ctors/.init_array sections to generate
output .init_array section.  Not all linkers support it.  This is a new
feature.  I don't want to cause any more trouble.

Currently, one can force to enable .init_array support by setting
enable_initfini_array to yes.

-- 
H.J.

  reply	other threads:[~2011-08-22 20:36 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-22  7:39 David Edelsohn
2011-08-22  7:44 ` H.J. Lu
2011-08-22  7:46   ` Jakub Jelinek
2011-08-22 14:23     ` H.J. Lu
2011-08-22 15:27       ` H.J. Lu
2011-08-22 15:46         ` Paolo Bonzini
2011-08-22 17:37     ` H.J. Lu
2011-08-22 18:33       ` H.J. Lu
2011-08-22 19:12       ` Joseph S. Myers
2011-08-22 19:19         ` H.J. Lu
2011-08-22 19:38           ` Joseph S. Myers
2011-08-22 20:50             ` H.J. Lu [this message]
2011-08-22  7:46   ` David Edelsohn
2011-08-22 16:26 ` H.J. Lu
  -- strict thread matches above, loose matches on Subject: below --
2011-03-21 18:40 H.J. Lu
2011-03-31 15:15 ` H.J. Lu
2011-04-14 19:11   ` H.J. Lu
2011-04-26 13:08   ` H.J. Lu
2011-05-18 17:30     ` H.J. Lu
2011-06-01 23:30       ` Carrot Wei
2011-06-03  4:31       ` H.J. Lu
2011-06-03 12:31         ` Richard Guenther
2011-06-03 12:52           ` H.J. Lu
2011-06-19 20:02             ` H.J. Lu
2011-06-19 21:31               ` Uros Bizjak
2011-07-22 12:31                 ` H.J. Lu
2011-07-22 12:36                   ` Rainer Orth
2011-07-22 12:36                     ` H.J. Lu
2011-07-22 13:20                       ` Rainer Orth
2011-07-22 12:37                   ` Jakub Jelinek
2011-07-22 13:21                     ` Joseph S. Myers
2011-07-22 13:29                     ` H.J. Lu
2011-07-22 14:17                       ` H.J. Lu
2011-07-22 14:55                         ` H.J. Lu
2011-08-06 14:51                           ` H.J. Lu
2011-08-09 14:32                             ` H.J. Lu
2011-08-14 19:20                               ` H.J. Lu
2011-08-19 10:05                           ` Jakub Jelinek
2011-08-19 14:58                             ` H.J. Lu
2011-08-19 15:54                               ` Jakub Jelinek
2011-08-20 21:16                                 ` H.J. Lu
2012-03-19 20:35                                   ` DJ Delorie
2012-03-19 20:40                                     ` Andrew Pinski
2012-03-19 20:42                                       ` DJ Delorie
2011-07-01 14:12               ` H.J. Lu
2011-06-03 17:13           ` Michael Eager

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='CAMe9rOpeQrSh_N4ELYnsme+ZvW7X1G1aK2q0F64=gx15eXeByw@mail.gmail.com' \
    --to=hjl.tools@gmail.com \
    --cc=dje.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=joseph@codesourcery.com \
    /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).