search for: mo_externalfunction

...king on the LLVM module. This greatly interferes with JIT-style multi-pass optimization and other things. Unfortunately, we are a long way from this though, as the lowering passes hack on the LLVM and other stuff does as well. Unless you have a good reason to do so, I would suggest trying to use MO_ExternalFunction just to make future refactoring easier. > There's another issue I don't understand. The module consists of functions and > constants. I'd expect that external function declarations are also constants, > with appropriate type. However, it seems they are not included in > [Mo...

Chris Lattner wrote: > > Second, MO_ExternalSymbol is used for storing name of external > > variable/function, right? Why it's not possible to use MO_GlobalAddress, > > where returned GlobalValue* has isExternal set to true? The > > GlobalValue::getName would return the name of the symbol. > > Using the GlobalValue is certainly the preferred way if you have it.

...ule. This greatly interferes > with JIT-style multi-pass optimization and other things. Unfortunately, > we are a long way from this though, as the lowering passes hack on the > LLVM and other stuff does as well. Unless you have a good reason to do > so, I would suggest trying to use MO_ExternalFunction just to make future > refactoring easier. I think I more or less understand this motivation. > > There's another issue I don't understand. The module consists of > > functions and constants. I'd expect that external function declarations > > are also constants, wi...