Good answers. Thanks! <div>I'm still learning a lot of the ghc code base, so I may have a few other questions like this as I try to familiarize with ghc code. </div><div><br></div><div>Is the dev list an ok forum for these sorts of questions?<span></span><br>
<br>On Saturday, May 18, 2013, Ian Lynagh wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Wed, May 15, 2013 at 12:45:01AM -0400, Carter Schonwald wrote:<br>
><br>
> <a href="https://github.com/ghc/ghc/blob/master/compiler/main/DriverPipeline.hs#L803which" target="_blank">https://github.com/ghc/ghc/blob/master/compiler/main/DriverPipeline.hs#L803which</a><br>
> mentions the -fvia-c backend in 2-3 places<br>
<br>
I've updated that, ta.<br>
<br>
> 2) when the ghc driver is used to manage building c code for subsequent ffi<br>
> usage, it doesn't seem possible to use a c compiler to do *.c -><br>
> *.o/dylib, instead it is only possible to do *.c-> *.s -> *.o/dylib.<br>
><br>
> I'm curious about reasons c,s,o choice that are still in play.<br>
<br>
Well, it means that GHC can be used to compile hand-written asm, and it<br>
also means that you can do "ghc -S". Also, there's been no reason to<br>
change it.<br>
<br>
<br>
--<br>
Ian Lynagh, Haskell Consultant<br>
Well-Typed LLP, <a href="http://www.well-typed.com/" target="_blank">http://www.well-typed.com/</a><br>
</blockquote></div>