[llvm-commits] [llvm] r87023 - /llvm/trunk/lib/CodeGen/AsmPrinter/DwarfException.cpp

Bill Wendling isanbard at gmail.com
Fri Nov 13 11:31:26 PST 2009


On Nov 13, 2009, at 2:12 AM, Duncan Sands wrote:

> Hi Bill,
>
>> If there's more than one function operand to a call instruction, be  
>> conservative
>> and don't assume that the call doesn't throw. It would be nice if  
>> there were a
>> way to determine which is the callee and which is a parameter. In  
>> practice, the
>> architecture we care about normally only have one operand for a  
>> call instruction
>> (x86 and arm).
>
> good idea!  Pity this is still not philosophically correct, i.e.  
> does not handle
> the case of a nounwind call to a function that is not marked  
> nounwind...
>
I talked with Dan about his proposal to put this information in a  
MachineMemOperand. It sounds like a good idea, but is more work than  
this. I'll investigate that.

-bw




More information about the llvm-commits mailing list