search for: sizedmemorycod

Displaying 10 results from an estimated 10 matches for "sizedmemorycod".

Did you mean: sizedmemorycode
[LLVMdev] Being able to know the jitted code-size before emitting
2008 Mar 30
3
[LLVMdev] Being able to know the jitted code-size before emitting
Hi everyone, vmkit requires to know the size of a jitted method before emitting the method. This allows to allocate the correct size for the method. The attached patch creates this functionality when the flag SizedMemoryCode is on. In order to implement this functionality, i had to virtualize some MachineCodeEmitter functions. Is it OK to commit the patch? Thanks, Nicolas -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: jit-size.patch URL: <http://lists.llv...
[LLVMdev] Being able to know the jitted code-size before emitting
2008 Apr 01
2
[LLVMdev] Being able to know the jitted code-size before emitting
...s Geoffray wrote: > > >> Hi everyone, >> >> vmkit requires to know the size of a jitted method before emitting >> the method. This allows to allocate the correct size for the method. >> The attached patch creates this functionality when the flag >> SizedMemoryCode is on. >> >> In order to implement this functionality, i had to virtualize some >> MachineCodeEmitter functions. >> >> Is it OK to commit the patch? >> >> Thanks, >> Nicolas >> Index: include/llvm/Target/TargetOptions.h >> =============...
[LLVMdev] Being able to know the jitted code-size before emitting
2008 Mar 31
0
[LLVMdev] Being able to know the jitted code-size before emitting
...On Mar 30, 2008, at 12:05 PM, Nicolas Geoffray wrote: > Hi everyone, > > vmkit requires to know the size of a jitted method before emitting > the method. This allows to allocate the correct size for the method. > The attached patch creates this functionality when the flag > SizedMemoryCode is on. > > In order to implement this functionality, i had to virtualize some > MachineCodeEmitter functions. > > Is it OK to commit the patch? > > Thanks, > Nicolas > Index: include/llvm/Target/TargetOptions.h > =====================================================...
[LLVMdev] Being able to know the jitted code-size before emitting
2008 Apr 01
0
[LLVMdev] Being able to know the jitted code-size before emitting
...gt; >> >>> Hi everyone, >>> >>> vmkit requires to know the size of a jitted method before emitting >>> the method. This allows to allocate the correct size for the method. >>> The attached patch creates this functionality when the flag >>> SizedMemoryCode is on. >>> >>> In order to implement this functionality, i had to virtualize some >>> MachineCodeEmitter functions. >>> >>> Is it OK to commit the patch? >>> >>> Thanks, >>> Nicolas >>> Index: include/llvm/Target/Targ...
[LLVMdev] Being able to know the jitted code-size before emitting
2008 Apr 04
3
[LLVMdev] Being able to know the jitted code-size before emitting
...;> Hi everyone, >>>> >>>> vmkit requires to know the size of a jitted method before emitting >>>> the method. This allows to allocate the correct size for the method. >>>> The attached patch creates this functionality when the flag >>>> SizedMemoryCode is on. >>>> >>>> In order to implement this functionality, i had to virtualize some >>>> MachineCodeEmitter functions. >>>> >>>> Is it OK to commit the patch? >>>> >>>> Thanks, >>>> Nicolas >>>...
[LLVMdev] Being able to know the jitted code-size before emitting
2008 Apr 05
2
[LLVMdev] Being able to know the jitted code-size before emitting
...; vmkit requires to know the size of a jitted method before emitting >>>>>> the method. This allows to allocate the correct size for the >>>>>> method. >>>>>> The attached patch creates this functionality when the flag >>>>>> SizedMemoryCode is on. >>>>>> >>>>>> In order to implement this functionality, i had to virtualize some >>>>>> MachineCodeEmitter functions. >>>>>> >>>>>> Is it OK to commit the patch? >>>>>> >>>&g...
[LLVMdev] Being able to know the jitted code-size before emitting
2008 Apr 05
0
[LLVMdev] Being able to know the jitted code-size before emitting
...method before >>>>>>> emitting >>>>>>> the method. This allows to allocate the correct size for the >>>>>>> method. >>>>>>> The attached patch creates this functionality when the flag >>>>>>> SizedMemoryCode is on. >>>>>>> >>>>>>> In order to implement this functionality, i had to virtualize >>>>>>> some >>>>>>> MachineCodeEmitter functions. >>>>>>> >>>>>>> Is it OK to commit...
[LLVMdev] Being able to know the jitted code-size before emitting
2008 Apr 04
0
[LLVMdev] Being able to know the jitted code-size before emitting
...;>>>> vmkit requires to know the size of a jitted method before emitting >>>>> the method. This allows to allocate the correct size for the >>>>> method. >>>>> The attached patch creates this functionality when the flag >>>>> SizedMemoryCode is on. >>>>> >>>>> In order to implement this functionality, i had to virtualize some >>>>> MachineCodeEmitter functions. >>>>> >>>>> Is it OK to commit the patch? >>>>> >>>>> Thanks, >>&...
[LLVMdev] Being able to know the jitted code-size before emitting
2008 Apr 07
2
[LLVMdev] Being able to know the jitted code-size before emitting
...;>>>>>>> emitting >>>>>>>> the method. This allows to allocate the correct size for the >>>>>>>> method. >>>>>>>> The attached patch creates this functionality when the flag >>>>>>>> SizedMemoryCode is on. >>>>>>>> >>>>>>>> In order to implement this functionality, i had to virtualize >>>>>>>> some >>>>>>>> MachineCodeEmitter functions. >>>>>>>> >>>>>>&gt...
[LLVMdev] Being able to know the jitted code-size before emitting
2008 Apr 07
0
[LLVMdev] Being able to know the jitted code-size before emitting
...;>>> emitting >>>>>>>>> the method. This allows to allocate the correct size for the >>>>>>>>> method. >>>>>>>>> The attached patch creates this functionality when the flag >>>>>>>>> SizedMemoryCode is on. >>>>>>>>> >>>>>>>>> In order to implement this functionality, i had to virtualize >>>>>>>>> some >>>>>>>>> MachineCodeEmitter functions. >>>>>>>>> >>&...