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 before > 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. 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 the developer having to rely on error reports to fix things (difficult, lots of work, slow progress). Options, on the other hand, would tend to perpetuate current entry barriers. I'm not too happy about either option, but probably a choice must be made. Which shall it be?> In addition to using a prebuilt binary.This would be simple, of course. Regards, Jo
On Mar 11, 2008, at 8:14 AM, Joachim Durchholz wrote:> 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 >> before >> 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. - Devang> > 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 > the > developer having to rely on error reports to fix things (difficult, > lots > of work, slow progress). > Options, on the other hand, would tend to perpetuate current entry > barriers. > > I'm not too happy about either option, but probably a choice must be > made. > Which shall it be? > >> In addition to using a prebuilt binary. > > This would be simple, of course. > > Regards, > Jo > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>> 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 >>> before >>> 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. OPTIMIZE_OPTION=-O2). -Tanya> > - > Devang >> >> 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 >> the >> developer having to rely on error reports to fix things (difficult, >> lots >> of work, slow progress). >> Options, on the other hand, would tend to perpetuate current entry >> barriers. >> >> I'm not too happy about either option, but probably a choice must be >> made. >> Which shall it be? >> >>> In addition to using a prebuilt binary. >> >> This would be simple, of course. >> >> Regards, >> Jo >> >> _______________________________________________ >> LLVM Developers mailing list >> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >