http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23756
Richard Guenther changed:
What|Removed |Added
Target|i486-linux-gnu |i?86-linux-gnu
Status|UNCO
--- Comment #4 from christophe dot guillon at st dot com 2010-01-28 16:20
---
Thanks for the detailled reply, I fully agree with your points:
- first, indeed, it's a matter of choice in the ABI (or compiler), the
assumption would be that a function that call another function of the same
--- Comment #3 from jakub at gcc dot gnu dot org 2010-01-28 15:37 ---
x86 ABI doesn't have any such guarantees.
Consider a function foo exported from the library which just calls this static
or visibility ("internal") function bar (but doesn't call any function through
PLT nor uses any g
--- Comment #2 from christophe dot guillon at st dot com 2010-01-28 14:55
---
This enhancement is still pending on gcc 4.4.3 on x86.
A function declared internal sets the GOT pointer while it could be avoided in
a callee-set-GOT model as on x86 ABI.
By defintion an internal function can
--- Comment #1 from christophe dot guillon at st dot com 2010-01-28 14:54
---
Created an attachment (id=19740)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19740&action=view)
Test case for the internal function enhancement
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23756
--
What|Removed |Added
Component|c |middle-end
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23756
