Re: global register variable clobbered by save/restore
Re: global register variable clobbered by save/restore
- Subject: Re: global register variable clobbered by save/restore
- From: "David N. Williams" <email@hidden>
- Date: Wed, 15 Sep 2004 08:54:34 -0400
- Organization: University of Michigan
Andrew Pinski wrote:
On Sep 12, 2004, at 6:27 AM, David N. Williams wrote:
I've had a problem with a rebuild of pfe-0.33.30 with gcc 3.3
under MacOS 10.3.4, which worked fine in 2.95.2 under MacOS
10.2.x. It seems to boil down to an illegal (I think)
save/restore of one or more registers declared as global
variables, which I've distilled into the example below.
Among several register problems, my initial scan of Bugzilla
doesn't show this, but maybe I missed it (or maybe I'm just
misunderstanding something).
Yes you missed that GCC has its own bugzilla and it was fixed
for GCC 3.4.0, I cannot remember the bug number off hand.
Thanks for the reply! It encouraged me to rescan the bugzillas.
I did not find the particular problem reported in my message
among the closed-bug reports, but of course I might have misssed
it again.
There was a lot about general register problems in gcc 3.x, and
the discussion in #10684 and #7871 makes me think that a fix for the
problems there could well include the problem here.
I did learn from those bugzillas that you have been involved
with the register problems, so I trust your memory! :-)
I'll wait to see if clobbering by save/restore is indeed fixed
in later versions of gcc. But since I don't use any gcc beyond
the Apple developer tools, that could be awhile? I work around
it now by turning off all global registers in pfe.
-- David
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden