--- Comment #2 from jkj at sco dot com 2005-10-07 10:57 ---
(In reply to comment #1)
> Because bar is not static to the TU, we can override it in a different one
> which causes use not to
> optimizate it out, try adding static infront of bar, baz, and larger.
>
> So thi
--- Comment #2 from jkj at sco dot com 2005-10-15 20:02 ---
Created an attachment (id=9990)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=9990&action=view)
This change to calls.c fixes the problem for me
I'm almost certain that there is a better way to do this, bu
--- Comment #3 from jkj at sco dot com 2005-10-15 20:14 ---
Created an attachment (id=9991)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=9991&action=view)
Sorry I uploaded the wrong diff. this is against mainline.
--
jkj at sco dot com changed:
What|
--- Comment #4 from jkj at sco dot com 2005-10-15 21:18 ---
Created an attachment (id=9993)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=9993&action=view)
New patch based on comments from Pinski
--
jkj at sco dot com changed:
What|
--- Comment #6 from jkj at sco dot com 2005-10-31 07:12 ---
rth has a completely different fix for this that is much more comprehensive.
http://gcc.gnu.org/ml/gcc/2005-10/msg00412.html has the details. I'm still
working on bringing my 4.1 tree up to speed so I can help him test
--- Additional Comments From jkj at sco dot com 2005-08-03 01:52 ---
FWIW, same problem occurs on UnixWare.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21291
--- Additional Comments From jkj at sco dot com 2005-08-04 00:57 ---
Just FYI, this still fails for me, from 3.4.4 all teh way up to the mainline,
when using -fPIC. Platform is UnixWare, but thats not significantly different
from the test point of view to any other x86 target. I dont
ary: Severe outages with -fPIC
Product: gcc
Version: 3.4.4
Status: UNCONFIRMED
Severity: critical
Priority: P1
Component: target
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: jkj at sco dot com
CC: gcc-bugs
--- Additional Comments From jkj at sco dot com 2005-08-04 04:03 ---
Wow. You sure are on top of things Andrew :)
Sorry I missed the -fPIC reports. The few I looked at didn't have them.
As for complex returns being broken on my target, do you by any chance have any
insight as to
--- Additional Comments From jkj at sco dot com 2005-08-11 09:18 ---
On UnixWare I have a very similar failure. It seems to be -fPIC that's wreaking
the havoc. I have an almost identical test case, and it aborts with:
terminate called after throwing an instance of 'int'
t
10 matches
Mail list logo
