search for: jitevent_emittedfunctiondetail

...er, but it means that during the compilation of vmkit, we need the sources of llvm. But, as we are currently developing a debian package of vmkit, we would like to avoid the installation of the llvm sources to compile vmkit. So, I made a small patch that just adds a new MachineCodeEmitter field in JITEvent_EmittedFunctionDetails and fill it in JITCodeEmitter. As the patch only adds a new field in the JITEvent_EmittedFunctionDetails, it should not break anything. At least, my llvm and my vmkit are still running :) (by the way, I had to execute a make clean before recompiling llvm because I think that a dependency is missin...

...> the compilation of vmkit, we need the sources of llvm. But, as we are > currently developing a debian package of vmkit, we would like to avoid the > installation of the llvm sources to compile vmkit. > > So, I made a small patch that just adds a new MachineCodeEmitter field in > JITEvent_EmittedFunctionDetails and fill it in JITCodeEmitter. As the patch > only adds a new field in the JITEvent_EmittedFunctionDetails, it should not > break anything. At least, my llvm and my vmkit are still running :) (by the > way, I had to execute a make clean before recompiling llvm because I think > that a...

...er, but it means that during the compilation of vmkit, we need the sources of llvm. But, as we are currently developing a debian package of vmkit, we would like to avoid the installation of the llvm sources to compile vmkit. So, I made a small patch that just adds a new MachineCodeEmitter field in JITEvent_EmittedFunctionDetails and fill it in JITCodeEmitter. As the patch only adds a new field in the JITEvent_EmittedFunctionDetails, it should not break anything. At least, my llvm and my vmkit are still running :) (by the way, I had to execute a make clean before recompiling llvm because I think that a dependency is missin...

...> the compilation of vmkit, we need the sources of llvm. But, as we are > currently developing a debian package of vmkit, we would like to avoid the > installation of the llvm sources to compile vmkit. > > So, I made a small patch that just adds a new MachineCodeEmitter field in > JITEvent_EmittedFunctionDetails and fill it in JITCodeEmitter. As the patch > only adds a new field in the JITEvent_EmittedFunctionDetails, it should not > break anything. At least, my llvm and my vmkit are still running :) (by the > way, I had to execute a make clean before recompiling llvm because I think > that a...

...of vmkit, we need the sources of llvm. But, as we are >> currently developing a debian package of vmkit, we would like to avoid the >> installation of the llvm sources to compile vmkit. >> >> So, I made a small patch that just adds a new MachineCodeEmitter field in >> JITEvent_EmittedFunctionDetails and fill it in JITCodeEmitter. As the patch >> only adds a new field in the JITEvent_EmittedFunctionDetails, it should not >> break anything. At least, my llvm and my vmkit are still running :) (by the >> way, I had to execute a make clean before recompiling llvm because I think...

...vmkit, we >> need the sources of llvm. But, as we are currently developing a >> debian package of vmkit, we would like to avoid the installation of the llvm sources to compile vmkit. >> >> So, I made a small patch that just adds a new MachineCodeEmitter >> field in JITEvent_EmittedFunctionDetails and fill it in >> JITCodeEmitter. As the patch only adds a new field in the >> JITEvent_EmittedFunctionDetails, it should not break anything. At >> least, my llvm and my vmkit are still running :) (by the way, I had >> to execute a make clean before recompiling llvm bec...

...t;> need the sources of llvm. But, as we are currently developing a >>> debian package of vmkit, we would like to avoid the installation of the llvm sources to compile vmkit. >>> >>> So, I made a small patch that just adds a new MachineCodeEmitter >>> field in JITEvent_EmittedFunctionDetails and fill it in >>> JITCodeEmitter. As the patch only adds a new field in the >>> JITEvent_EmittedFunctionDetails, it should not break anything. At >>> least, my llvm and my vmkit are still running :) (by the way, I had >>> to execute a make clean before recompil...

...; we need the sources of llvm. But, as we are currently developing a >>> debian package of vmkit, we would like to avoid the installation of the llvm sources to compile vmkit. >>> >>> So, I made a small patch that just adds a new MachineCodeEmitter >>> field in JITEvent_EmittedFunctionDetails and fill it in >>> JITCodeEmitter. As the patch only adds a new field in the >>> JITEvent_EmittedFunctionDetails, it should not break anything. At >>> least, my llvm and my vmkit are still running :) (by the way, I had >>> to execute a make clean before reco...

...sources of llvm. But, as we are currently developing a >>>> debian package of vmkit, we would like to avoid the installation of the llvm sources to compile vmkit. >>>> >>>> So, I made a small patch that just adds a new MachineCodeEmitter >>>> field in JITEvent_EmittedFunctionDetails and fill it in >>>> JITCodeEmitter. As the patch only adds a new field in the >>>> JITEvent_EmittedFunctionDetails, it should not break anything. At >>>> least, my llvm and my vmkit are still running :) (by the way, I had >>>> to execute a make clean...

...But, as we are currently developing a >>>>> debian package of vmkit, we would like to avoid the installation of the llvm sources to compile vmkit. >>>>> >>>>> So, I made a small patch that just adds a new MachineCodeEmitter >>>>> field in JITEvent_EmittedFunctionDetails and fill it in >>>>> JITCodeEmitter. As the patch only adds a new field in the >>>>> JITEvent_EmittedFunctionDetails, it should not break anything. At >>>>> least, my llvm and my vmkit are still running :) (by the way, I had >>>>> to exec...

...ut, as we are currently >>>>> developing a debian package of vmkit, we would like to avoid the installation of the llvm sources to compile vmkit. >>>>> >>>>> So, I made a small patch that just adds a new MachineCodeEmitter >>>>> field in JITEvent_EmittedFunctionDetails and fill it in >>>>> JITCodeEmitter. As the patch only adds a new field in the >>>>> JITEvent_EmittedFunctionDetails, it should not break anything. At >>>>> least, my llvm and my vmkit are still running :) (by the way, I >>>>> had to...

...currently >>>>>> developing a debian package of vmkit, we would like to avoid the installation of the llvm sources to compile vmkit. >>>>>> >>>>>> So, I made a small patch that just adds a new MachineCodeEmitter >>>>>> field in JITEvent_EmittedFunctionDetails and fill it in >>>>>> JITCodeEmitter. As the patch only adds a new field in the >>>>>> JITEvent_EmittedFunctionDetails, it should not break anything. At >>>>>> least, my llvm and my vmkit are still running :) (by the way, I >>>>>...

...gt;>>>>> currently developing a debian package of vmkit, we would like to avoid the installation of the llvm sources to compile vmkit. >>>>>> >>>>>> So, I made a small patch that just adds a new MachineCodeEmitter >>>>>> field in JITEvent_EmittedFunctionDetails and fill it in >>>>>> JITCodeEmitter. As the patch only adds a new field in the >>>>>> JITEvent_EmittedFunctionDetails, it should not break anything. At >>>>>> least, my llvm and my vmkit are still running :) (by the way, I >>>>...