It seems that bugpoint (and llvmc2, etc.) is hard-wired to use gcc to do
assembling and linking. I want to bugpoint-reduce a testcase that came
from Fortran and so I need to invoke our compiler to do at least the linking
step to get our Fortran libraries.
Is there a way to do this via bugpoint's command-line interface or do I
have to hack bugpoint's source? I can see how I might make the GCC
class a subclass of some ReferenceCompiler class and then abstract
our compiler's interface in the same way (reimplementing ExecuteProgram
and friends.
-Dave
Hi Dave,> It seems that bugpoint (and llvmc2, etc.) is hard-wired to use gcc to do > assembling and linking. I want to bugpoint-reduce a testcase that came > from Fortran and so I need to invoke our compiler to do at least the linking > step to get our Fortran libraries.you can always cheat and have gcc be a symlink to your compiler. Ciao, Duncan.
On Saturday 12 July 2008 02:47, Duncan Sands wrote:> Hi Dave, > > > It seems that bugpoint (and llvmc2, etc.) is hard-wired to use gcc to do > > assembling and linking. I want to bugpoint-reduce a testcase that came > > from Fortran and so I need to invoke our compiler to do at least the > > linking step to get our Fortran libraries. > > you can always cheat and have gcc be a symlink to your compiler.Except the flags aren't right. For example, our compiler doesn't accept -x. I think this would be a useful feature for bugpoint. I've almost got an initial implementation done. More stuff to send back once red tape clears. :) -Dave