This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] sparc64-linux multilibs]
- To: dann at ics dot uci dot edu
- Subject: Re: [PATCH] sparc64-linux multilibs]
- From: "David S. Miller" <davem at redhat dot com>
- Date: Wed, 8 Dec 1999 00:07:32 -0800
- CC: rth at cygnus dot com, jakub at redhat dot com, gcc-patches at egcs dot cygnus dot com
- References: <199912071406.aa26354@gremlin-relay.ics.uci.edu>
From: Dan Nicolaescu <dann@ics.uci.edu>
Date: Tue, 07 Dec 1999 14:06:09 -0800
I think at least _bb.o from libgcc.a should be built with
-mno-app-regs
Some of the __bb_* functions are not allowed to change the state of
the processor, if they use they use the app-regs then the
MACHINE_SAVE_STATE macro hould save those registers too.
What is the allowed use of app-regs anywhay? At some point I was
looking for some info about this, but I didn't find anything...
You have to be careful. The whole point behind app-regs is that
this way a thread library implementation can keep pointers to
thread-specific data in a few globals, if you do this for _bb.o
then you cannot use it for threaded programs.
But like Richard said, use profile-arcs instead for this stuff.
Later,
David S. Miller
davem@redhat.com