Displaying 3 results from an estimated 3 matches for "pendingglobals".
2005 Feb 20
0
[LLVMdev] Attempt #1: JIT Thread Safety
...ed too early. The data structures
that are protected are:
ExecutionEngine:
std::map<const GlobalValue*, void *> GlobalAddressMap; // R/W data
structure
std::map<void *, const GlobalValue*> GlobalAddressReverseMap; // R/W
data structure
JIT:
std::vector<const GlobalVariable*> PendingGlobals; // R/W data
structure
FunctionPassManager PM; // Could call passes which are not thread safe
Both of these classes have additional members which I have not
protected. It looked to my brief analysis that they were used in a
read-only fashion. Can anyone tell me if I am wrong:
ExecutionEngin...
2009 Mar 16
0
[LLVMdev] MachO and ELF Writers/MachineCodeEmittersarehard-codedinto LLVMTargetMachine
...CodeEmitter
- a MachineCodeEmitter. Friend class of MachOWriter (friend class
== broken encapsulation!?)
startFunction allocates storage in the text section for the current function.
finishFunction emits constant-pools, jumptables; transforms
relocations adding globals to the MachOWriter's PendingGlobals list,
and all relocations to the parent section's relocation list; adds a
symbol for the function to the MachOWriter's SymbolTable.
[In general, all the operations in finishFunction actually modify the
data of the MachOWriter. Shouldn't these be pushed into the
MachOWriter? ]
3. X86C...
2009 Mar 16
2
[LLVMdev] MachO and ELF Writers/MachineCodeEmittersarehard-codedinto LLVMTargetMachine
>> Sorry, I disagree actually the MachineCodeEmitter or the
>> 'MachineCodeWritter' does not do any file handling at all. Do look at the
>> code for the MachineCodeWritter and you will see it only writes to memory
>> and if it reaches the end of the allotted memory I believe higher ordered
>> logic reallocates a larget buffer and starts again from scratch.