On Apr 22, 2005, at 9:52 AM, Chris Lattner wrote:> On Fri, 22 Apr 2005, Andrew Lenharth wrote: >>> Does that make sense or do you have a better idea? >> >> -enable-targets=x86,alpha,sparcv9 >> -link-targets=alpha,host >> >> Valid options for both are: >> the names of the targets >> host >> all >> >> where all is the default for both items >> >> I have in my tree the patch to partially support this (well the link >> half of it). Right now I am controlling linking with a variable in >> the >> toplevel makefile until a config patch like this goes in. > > I think this makes the most sense. I assume that > enabled-but-not-linked targets are built into shared objects?This makes sense to to me too, except I agree with a couple of the others that it would be most convenient to build only for the host machine by default. That is nearly always needed and most likely to minimize redundant compile/link time.> > My one concern about this change is that it makes it more likely for > people to break the build on hosts not equal to their own. However, > as long as the nightly testers due the full build, I dpm > t think this is a big problem. > > -Chris > > -- > http://nondot.org/sabre/ > http://llvm.cs.uiuc.edu/ > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev
On Fri, 22 Apr 2005, Andrew Lenharth wrote:>> Does that make sense or do you have a better idea? > > -enable-targets=x86,alpha,sparcv9 > -link-targets=alpha,host > > Valid options for both are: > the names of the targets > host > all > > where all is the default for both items > > I have in my tree the patch to partially support this (well the link > half of it). Right now I am controlling linking with a variable in the > toplevel makefile until a config patch like this goes in.I think this makes the most sense. I assume that enabled-but-not-linked targets are built into shared objects? My one concern about this change is that it makes it more likely for people to break the build on hosts not equal to their own. However, as long as the nightly testers due the full build, I dpm t think this is a big problem. -Chris -- http://nondot.org/sabre/ http://llvm.cs.uiuc.edu/
On Fri, 22 Apr 2005, Vikram S. Adve wrote:>> I think this makes the most sense. I assume that enabled-but-not-linked >> targets are built into shared objects? > > This makes sense to to me too, except I agree with a couple of the others > that it would be most convenient to build only for the host machine by > default. That is nearly always needed and most likely to minimize redundant > compile/link time.To me, getting testing is more important than user convenience in this case. In particular, people who build on slow machines often can just use the configure option to just build and link in the target matching the host. If we default to building everything then new users (or people who want to test everything on a regular basis) will build everything by default, but people on slow machines can choose to disable certain chunks. -Chris -- http://nondot.org/sabre/ http://llvm.cs.uiuc.edu/