This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
RE: indirect call in RTL dump files
- From: "Dave Korn" <dave dot korn at artimi dot com>
- To: "'sean yang'" <seanatpurdue at hotmail dot com>, <pinskia at physics dot uc dot edu>
- Cc: <gcc at gcc dot gnu dot org>
- Date: Mon, 8 May 2006 14:11:15 +0100
- Subject: RE: indirect call in RTL dump files
On 06 May 2006 19:45, sean yang wrote:
>> From: Andrew Pinski
>> On May 6, 2006, at 10:06 AM, sean yang wrote:
>>
>>> 2) indirect call (explained in 3.1 in the above paper)
>>> Can someone help me explain this a bit? --what the corresponding code is
>>> in C, and what causes it to happen? What does the RTL code look like?
>>
>>
>> void f(void (*x)(void))
>> {
>> x();
>> }
> Thanks very much. Is this (callback) the only case for indirect call?
>
No, lots of targets are obliged to generate indirect calls to overcome
limitations with branch instruction ranges. See ARM and rs6000 longcall
options/attributes for examples.
cheers,
DaveK
--
Can't think of a witty .sigline today....