From: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
To: Geoff Keating <geoffk@ozemail.com.au>
Cc: amylaar@cygnus.co.uk, law@cygnus.com, ghazi@snafu.Rutgers.EDU,
davem@cobaltmicro.com, egcs@egcs.cygnus.com
Subject: Re: PIC register allocation by reload (Was: Re: egcs-1.2 stuff)
Date: Mon, 31 May 1999 21:36:00 -0000 [thread overview]
Message-ID: <4.2.0.37.19990506233202.036d7400@mail.lauterbach.com> (raw)
Message-ID: <19990531213600.qT2qe7pY9-bXEZ2paQysU2mxUYylbXRvbpccQv5hxws@z> (raw)
In-Reply-To: <199905062115.HAA00514@geoffk.wattle.id.au>
At 23:15 06.05.99 , Geoff Keating wrote:
>Is this testcase already in the test suite? It's stripped-down code
>from kaffe's implementation of GNU zip.
Geoff,
this testcase is not in the testsuite, but it also no longer FAILs with the
current cvs-egcs, reload got a _lot_ smarter since egcs-1.1. But there's
one testcase in the testsuite which still shows this problem with -fpic on
PPC, attached below.
Franz.
PS. Geoff, if you want to play with the egcs-mainline a bit, login into the
LinuxPPC developers machine, you'll find everything under ~fsirl/egcsm
(source) and ~fsirl/obj/cvsm (build from today), you should have full
access there.
gcc/testsuite/gcc.dg/980523-1.c:
/* { dg-do run { target rs6000-*-linux* powerpc-*-linux*} } */
/* { dg-options "-O2 -fpic" } */
void foo1(int a, char *b, int c)
{
c =a+c+234;
}
int foo2(int d)
{
return d*d;
}
int bar1, bar2, bar3;
char * bar4;
int main(void) {
int h;
bar1 = foo2(1);
bar2 = foo2(1);
h = foo2(1);
foo1(1, "a", foo2(1));
foo1(bar1, "a", foo2(1));
foo2(1);
h = foo2(1);
bar3 = 1;
bar4 = "a";
foo1(1, "n", foo2(1));
foo1(1, "o", foo2(1));
foo1(1, "p", foo2(1));
foo1(bar1, "a", foo2(1));
bar3 = h;
bar4 = "b"; foo1(bar1, "b", foo2(1));
foo1(1, "q", foo2(1));
bar4 = "c"; foo1(1, "c", foo2(1));
bar4 = "d"; foo1(1, "d", foo2(1));
bar4 = "e"; foo1(1, "e", foo2(1));
bar4 = "f"; foo1(1, "f", foo2(1));
bar4 = "g"; foo1(1, "g", foo2(1));
bar4 = "h"; foo1(1, "h", foo2(1));
bar4 = "i"; foo1(1, "i", foo2(1));
bar4 = "j"; foo1(1, "j", foo2(1));
bar4 = "k"; foo1(1, "k", foo2(1));
bar4 = "l"; foo1(1, "l", foo2(1));
bar4 = "m";
foo1(bar2, "m", foo2(1));
exit(0);
}
next prev parent reply other threads:[~1999-05-31 21:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-28 6:12 egcs-1.2 stuff Kaveh R. Ghazi
1999-03-28 6:24 ` David Miller
1999-03-31 23:46 ` David Miller
1999-03-28 13:09 ` Jeffrey A Law
1999-03-28 16:06 ` David Miller
1999-03-31 23:46 ` David Miller
1999-03-31 23:46 ` Jeffrey A Law
1999-04-30 10:46 ` PIC register allocation by reload (Was: Re: egcs-1.2 stuff) Joern Rennecke
1999-04-30 23:15 ` Joern Rennecke
1999-05-06 13:36 ` Franz Sirl
1999-05-06 14:16 ` Geoff Keating
1999-05-06 14:45 ` Franz Sirl [this message]
1999-05-13 1:12 ` Jeffrey A Law
1999-05-31 21:36 ` Jeffrey A Law
1999-05-18 21:33 ` Geoff Keating
1999-05-31 21:36 ` Geoff Keating
1999-05-31 21:36 ` Franz Sirl
1999-05-31 21:36 ` Geoff Keating
1999-05-31 21:36 ` Franz Sirl
1999-03-31 23:46 ` egcs-1.2 stuff Kaveh R. Ghazi
1999-05-06 18:53 PIC register allocation by reload (Was: Re: egcs-1.2 stuff) Kaveh R. Ghazi
1999-05-31 21:36 ` Kaveh R. Ghazi
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=4.2.0.37.19990506233202.036d7400@mail.lauterbach.com \
--to=franz.sirl-kernel@lauterbach.com \
--cc=amylaar@cygnus.co.uk \
--cc=davem@cobaltmicro.com \
--cc=egcs@egcs.cygnus.com \
--cc=geoffk@ozemail.com.au \
--cc=ghazi@snafu.Rutgers.EDU \
--cc=law@cygnus.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).