<div dir="ltr"><div><div>Hi Jan-Simon,<br><br>I appreciate the quick reply. I am not currently using the build system so I appreciate the insight. <br><br></div>So I believe from what you wrote LLVMLinux can emit the IR but does not use it for final compilation. Is there LLVM IR->bzImage support?<br><br></div>Thanks again,<br><br>Jason<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Dec 4, 2014 at 3:50 PM, Jan-Simon Moeller <span dir="ltr"><<a href="mailto:dl9pf@gmx.de" target="_blank">dl9pf@gmx.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Jason,<br>
Am Donnerstag, 4. Dezember 2014, 15:10:13 schrieb Jason Gionta:<br>
<span class="">> Hello all,<br>
><br>
> I was wondering if someone has looked at or has experience outputting LLVM<br>
> IR of LLVMLinux before linking. I hope to better understand the feasibility<br>
> of deploying IR to perform LTO per machine before final linkage. Does<br>
> anyone have ideas on how much effort would it take to enable in the current<br>
> LLVMLinux build process (basically the linux build system)?<br>
><br>
> Thanks,<br>
<br>
</span>This works already with the LLVMLinux build system. Actually we compile every<br>
file twice. One normal compilation and a run for IR .<br>
<br>
cd targets/<yourtarget - eg x86> ; make BITCODE=1<br>
<br>
from make help<br>
* make BITCODE=1 - Output llvm bitcode to *.bc files<br>
<br>
Best,<br>
Jan-Simon<br>
<br>
</blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature">Jason Gionta<br>Cyber Defense Lab<br>North Carolina State University<br><a href="mailto:jjgionta@ncsu.edu">jjgionta@ncsu.edu</a></div>
</div>