From: Roland McGrath <roland@redhat.com>
To: davidm@hpl.hp.com
Cc: libc-hacker@sources.redhat.com
Subject: Re: [PATCH] move __gmon_start__ call out of .init section
Date: Thu, 07 Nov 2002 13:45:00 -0000 [thread overview]
Message-ID: <200211072145.gA7Ljlb28956@magilla.sf.frob.com> (raw)
In-Reply-To: David Mosberger's message of Tuesday, 29 October 2002 23:22:12 -0800 <200210300722.g9U7MCXs000818@napali.hpl.hp.com>
> The patch below changes the ia64 initfini.c such that the call to
> __gmon_start__ is done via the .init_array section (if available).
> The idea here is to keep the .init/.fini empty (apart from
> prologue/epilogue) so as to ensure that the unwind info is always
> correct.
Can you elaborate a bit on the problem you are addressing here?
This seems wrong to me, in that the user program might put some code into
the .init section and then __gmon_start__ would come after it instead of
before.
next prev parent reply other threads:[~2002-11-07 21:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-30 7:00 David Mosberger
2002-11-07 13:45 ` Roland McGrath [this message]
2002-11-07 14:08 ` David Mosberger
2002-11-07 14:27 ` Roland McGrath
2002-11-07 14:32 ` David Mosberger
2002-11-07 17:43 ` Roland McGrath
2002-11-08 3:05 ` Andreas Schwab
2002-11-08 11:15 ` 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=200211072145.gA7Ljlb28956@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=davidm@hpl.hp.com \
--cc=libc-hacker@sources.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).