[LLVMdev] NewNightlyTester.pl: split into phases?
Tanya M. Lattner
tonic at nondot.org
Tue Mar 11 10:41:31 PDT 2008
>> Am Samstag, den 08.03.2008, 14:02 -0800 schrieb Tanya Lattner:
>>> - ability to check out llvm-gcc or update llvm-gcc and build it
>>> running tests.
>> This seems to be a bit more complicated than I thought. There are
>> variations in the build process depending on whether it's a Darwin
>> system or not, installed gcc version, and presence or absence of
>> multilib extensions. I'm not sure that a simple-minded script can
>> reliably detect all the differences.
> IIUC, all target specific variations are in llvm-gcc configure
> options. In the beginning it is OK to let user specify llvm-gcc
> configure options.
I was going to suggest this as well. We should make it *really* simple in
that you just specifiy the configure line options (environment variable?)
and then we may need a couple extra building options for LLVM (ie.
>> The alternative would be options and letting the user configure.
>> Writing a script would be a difficult task, since it would have to be
>> tested on as many architectures and configurations as possible, with
>> developer having to rely on error reports to fix things (difficult,
>> of work, slow progress).
>> Options, on the other hand, would tend to perpetuate current entry
>> I'm not too happy about either option, but probably a choice must be
>> Which shall it be?
>>> In addition to using a prebuilt binary.
>> This would be simple, of course.
>> LLVM Developers mailing list
>> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
More information about the llvm-dev