<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Oct 2, 2009, at 8:14 PM, Mark A. Miller wrote:</div><blockquote type="cite"><div>As a preface, I am not a compiler developer, so please take my questions with a grain of salt. But there doesn't appear to be a clang-user mailing list, so I'm posting to -dev.</div><div><br></div><div>I'm extremely interested in clang, since it both attempts to be saner than what gcc has become, and doesn't have the community forking licensing issues of GPLv2 and GPLv3. My recent projects have involved building cross-compilers for various targets, such as ARM, MIPS, PPC, sh4, et cetera.</div>
<div><br></div><div>My main question is, has any work been done on allowing clang to cross-compile various targets? I found the following bug: <a href="http://llvm.org/bugs/show_bug.cgi?id=4127">http://llvm.org/bugs/show_bug.cgi?id=4127</a> which indicated that it was still a work in progress. </div>
<div><br></div><div>Also, I suppose this question may be better posed to the llvm list, but is there any documentation on how to use a gcc frontend and llvm backend to cross-compile? </div><div><br></div><div>Lastly, and this is more of a slight nitpick issue, since I managed to find the bug with the following mailing list post: <a href="http://article.gmane.org/gmane.comp.compilers.clang.devel/5893">http://article.gmane.org/gmane.comp.compilers.clang.devel/5893</a> I'd point out that the -arch feature currently only works on MacOSX. I wasted several hours trying to figure out what I was doing wrong on my Linux installation until I found ths out.</div>
</blockquote></div><br><div>Hi Mark,</div><div><br></div><div>This is an area that we are actively interested in involving, but no one is driving yet. Are you interested in helping out? I'm not too familiar with the issues and Daniel (who is most knowledgeable about the driver) is out on vacation for 2 weeks.</div><div><br></div><div>-Chris </div></body></html>