Displaying 5 results from an estimated 5 matches for "profileloader".
2009 Sep 09
2
[LLVMdev] [PATCH] & Question: Preserving ProfileInfo for backend.
...4bd65dbe84394bb7
noted that accessing execution counts in a MachineFunction pass (using
the BasicBlock* corresponding to the respective MachineBasicBlock)
returned 0 for all blocks. Running llc with --debug-pass=Structure I
noticed that the NoProfileInfo pass was being executed. I tried
adding a ProfileLoaderPass in the addPreRegAlloc function of the X86
target machine to load the profile information but receive the
following runtime error when the pass manager attempts to add the
ProfileLoader pass:
llc: <path to llvm>/llvm/lib/VMCore/PassManager.cpp:1597: virtual void
llvm::ModulePass::assignPa...
2009 Sep 08
0
[LLVMdev] [PATCH] & Question: Preserving ProfileInfo for backend.
On Sep 8, 2009, at 1:27 AM, Andreas Neustifter wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,
>
> the second part of my work is to preserve the profiling information
> through all the transformation passes and make it available to the
> backend machinery.
>
> Attached is an example patch on how I plan to preserve the information
> for a given
2007 Aug 21
0
[LLVMdev] profile directed pass with 'extern' profile data
Hi,
is there a pass for profile-directed optimization or transformation,
which doesn't use ProfileInfo- and ProfileLoader-class?
Perhaps in a project based on LLVM that uses profile data generated
'outside' of the standard LLVM-chain shown in 'profile.pl'?
Is there an example for such a pass I've slipped?
Kind regards,
Nico
2009 Sep 09
0
[LLVMdev] [PATCH] & Question: Preserving ProfileInfo for backend.
...respective MachineBasicBlock)
> returned 0 for all blocks. Running llc with I
> noticed that the NoProfileInfo pass was being executed.
Yes, llc currently does not support the loading of profiles, but I
attach a patch that does that, can you try that please?
> I tried
> adding a ProfileLoaderPass in the addPreRegAlloc function of the X86
> target machine to load the profile information but receive the
> following runtime error when the pass manager attempts to add the
> ProfileLoader pass:
>
> llc: <path to llvm>/llvm/lib/VMCore/PassManager.cpp:1597: virtual void
&...
2009 Sep 08
2
[LLVMdev] [PATCH] & Question: Preserving ProfileInfo for backend.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
the second part of my work is to preserve the profiling information
through all the transformation passes and make it available to the
backend machinery.
Attached is an example patch on how I plan to preserve the information
for a given transformation pass.
And now comes the question into place: whats the best way to attach the
profile info