public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: Roland McGrath <roland@redhat.com>
Cc: davidm@hpl.hp.com, libc-hacker@sources.redhat.com, hjl@lucon.org
Subject: Re: patch to make init_array work (2nd version; resend)
Date: Thu, 07 Nov 2002 14:38:00 -0000	[thread overview]
Message-ID: <15818.60269.685537.688317@napali.hpl.hp.com> (raw)
In-Reply-To: <200211072229.gA7MTOY29236@magilla.sf.frob.com>

>>>>> On Thu, 7 Nov 2002 14:29:24 -0800, Roland McGrath <roland@redhat.com> said:

  >> Perhaps, but it would defeat the whole purpose of switching to
  >> init_array (see my previous mail about why any call in
  >> .init/.fini causes incorrect unwind info).

  Roland> Since this part of the section is generated normally along
  Roland> with the prologue, I would think that its unwind info would
  Roland> come out normally too.

For .init, wouldn't the new code have to go into the epilogue to
ensure that the .init_array entries are called after .init?

	--david

  reply	other threads:[~2002-11-07 22:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-07 11:43 David Mosberger
2002-11-07 13:31 ` Roland McGrath
2002-11-07 13:51   ` David Mosberger
2002-11-07 13:58     ` Roland McGrath
2002-11-07 14:10       ` David Mosberger
2002-11-07 14:29         ` Roland McGrath
2002-11-07 14:38           ` David Mosberger [this message]
2002-11-07 18:10       ` Richard Henderson
2002-11-07 18:20         ` Roland McGrath
2002-11-07 18:30           ` David Mosberger
2002-11-07 18:45             ` Roland McGrath
2002-11-08 11:34 Roland McGrath
2002-11-08 11:38 ` David Mosberger

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=15818.60269.685537.688317@napali.hpl.hp.com \
    --to=davidm@napali.hpl.hp.com \
    --cc=davidm@hpl.hp.com \
    --cc=hjl@lucon.org \
    --cc=libc-hacker@sources.redhat.com \
    --cc=roland@redhat.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).