public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Geoff Keating <geoffk@geoffk.org> 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: Wed, 17 Jul 2002 12:16:00 -0000 [thread overview] Message-ID: <20020717191601.17633.qmail@sources.redhat.com> (raw) The following reply was made to PR other/7114; it has been noted by GNATS. From: Geoff Keating <geoffk@geoffk.org> To: dje@watson.ibm.com Cc: amodra@bigpond.net.au, d.mueller@elsoft.ch, gcc-gnats@gcc.gnu.org, gcc-patches@gcc.gnu.org Subject: Re: other/7114: ICE building strcoll.op from glibc-2.2.5 Date: Wed, 17 Jul 2002 12:10:12 -0700 > cc: amodra@bigpond.net.au, d.mueller@elsoft.ch, gcc-gnats@gcc.gnu.org, > gcc-patches@gcc.gnu.org > Date: Wed, 17 Jul 2002 11:42:02 -0400 > From: David Edelsohn <dje@watson.ibm.com> > > >>>>> Geoff Keating writes: > > Geoff> So, thanks for testing it! We now know this doesn't work. :-) > > The patch was tested on SVR4 by Franz and showed no new failures: > > http://gcc.gnu.org/ml/gcc-patches/1999-03n/msg00584.html The testsuite probably doesn't check that r30 is not clobbered in a nested function when profiling is switched on. Actually, Alan, could you write a test for that? (That's something I missed while reviewing your patch.) > PUSH/POP cannot work on PowerPC. On AIX PUSH/POP were corrupting the > stack. Because they were implemented wrongly? Clearly, push/pop can work, because procedures push and pop call frames all the time. It's just necessary to do it the right way. For AIX, of course, push/pop is unnecessary, and Alan's patch didn't add it. -- - Geoffrey Keating <geoffk@geoffk.org> <geoffk@redhat.com>
next reply other threads:[~2002-07-17 19:16 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-07-17 12:16 Geoff Keating [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-07-17 13:36 David Edelsohn 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 22:16 Alan Modra 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=20020717191601.17633.qmail@sources.redhat.com \ --to=geoffk@geoffk.org \ --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).