search for: namemangler

...e names, because LLVM has a > unusual mechanism where it allows objects with different types to have > the same name. This means you can have: > > int %foo(int %X) { ret int %X } > float %foo(float %X) { ret float %X } > > In the context of a code generator, you should use the NameMangler > interface to make everything just work. > > If you're doing something else and think you need the symbol table, please > let me know. Clients of the SymbolTable class are extremely rare (by > design). The SymbolTable class is mostly an internal class that is > automagicall...

...ecommend depending too much on the names, because LLVM has a unusual mechanism where it allows objects with different types to have the same name. This means you can have: int %foo(int %X) { ret int %X } float %foo(float %X) { ret float %X } In the context of a code generator, you should use the NameMangler interface to make everything just work. If you're doing something else and think you need the symbol table, please let me know. Clients of the SymbolTable class are extremely rare (by design). The SymbolTable class is mostly an internal class that is automagically used by the system to provi...

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.

The company I work for uses samba to allow access to Unix files from PCs running Windows 95. When I create a file from my PC on the samba drive with a name including upper case letters, the name is forced into all lower case: I cannot create a file name containing an upper case letter. From Unix, I can create (and see from my PC) mixed-case file names. I asked my system administrator