public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Alan Modra <amodra@bigpond.net.au> To: amodra@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: other/7114: ICE building strcoll.op from glibc-2.2.5 Date: Mon, 15 Jul 2002 22:16:00 -0000 [thread overview] Message-ID: <20020716051601.1079.qmail@sources.redhat.com> (raw) The following reply was made to PR other/7114; it has been noted by GNATS. From: Alan Modra <amodra@bigpond.net.au> To: Richard Henderson <rth@redhat.com>, Geoff Keating <geoffk@redhat.com>, d.mueller@elsoft.ch, gcc-gnats@gcc.gnu.org, gcc-patches@gcc.gnu.org, dje@watson.ibm.com Cc: Subject: Re: other/7114: ICE building strcoll.op from glibc-2.2.5 Date: Tue, 16 Jul 2002 14:38:08 +0930 On Mon, Jul 15, 2002 at 09:31:24PM -0700, Richard Henderson wrote: > On Tue, Jul 16, 2002 at 11:08:16AM +0930, Alan Modra wrote: > > It gets worse. rs6000/sysv4.h sets PROFILE_BEFORE_PROLOGUE. > > Make rs6000/sysv4.h can use PROFILE_HOOK instead. Aye, that's the nice way to do it. However, on powerpc64-linux, I've had kernel people complaining that the profiling code isn't what they want: All those register saves from the prologue preceding the mcount call apparently are messing up accurate count values, and it's hard for an mcount implementation to adjust times, or so I'm told. I implemented a simple hack to do PROFILE_BEFORE_PROLOGUE on powerpc64-linux for people who want it. I suspect we'll get the same sort of complaint if we change powerpc mcount. There's also the issue that some special-purpose mcount functions may expect to be called before the stack has been adjusted. I'm rapidly approaching the point where I either give up on this problem, or simply remove support for profiling on nested functions. The current code just doesn't work.
next reply other threads:[~2002-07-16 5:16 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-07-15 22:16 Alan Modra [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-07-17 13:36 David Edelsohn 2002-07-17 12:16 Geoff Keating 2002-07-17 12:06 Geoff Keating 2002-07-17 10:46 David Edelsohn 2002-07-17 8:46 David Edelsohn 2002-07-17 2:06 Alan Modra 2002-07-17 0:16 Geoff Keating 2002-07-16 21:16 Alan Modra 2002-07-16 18:56 Alan Modra 2002-07-16 10:56 Geoff Keating 2002-07-16 10:46 Geoff Keating 2002-07-15 21:36 Richard Henderson 2002-07-15 18:46 Alan Modra 2002-07-15 16:56 Alan Modra 2002-07-15 12:46 Geoff Keating 2002-07-15 2:36 Alan Modra 2002-06-25 2:16 d.mueller
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=20020716051601.1079.qmail@sources.redhat.com \ --to=amodra@bigpond.net.au \ --cc=amodra@gcc.gnu.org \ --cc=gcc-prs@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: linkBe 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).