On Mon, May 31, 2010 at 3:44 PM, Garrett Cooper <yanefbsd_at_gmail.com> wrote: > I personally would much rather have the glue in place to switch > between compilers and have things default to the base version of gcc > than just magically switch the compiler over to clang. > >From all the threads I've read on this subject, that's exactly what is planned: - import clang into the source tree - add knobs to select which compiler to use - leave GCC as the default compiler IOW, unless you actually want to test clang and set the appropriate knobs, then nothing will change for you. Everything works as per normal. I really don't see what the big deal is, or why everyone is getting their knickers in a knot over this. GCC isn't being removed from the tree. GCC is staying the default compiler. The sky is not falling. If you want to test clang, you can. If you don't want to test clang, you aren't forced to in any way, shape, or form. It's really no different from the processes used when adding libthread alongside libkse, or add sched_ule alongside sched_bsd. The defaults didn't change, both were available, and everyone carried on without issues while those motivated to test the new bits did so. Eventually, enough bugs were found and fixed, things stabilised, and the new bits became the default. Similar process here. I may be only a lowly user and occasional tested of new bits, but I really don't understand the mountain people are making of this ant hill. -- Freddie Cash fjwcash_at_gmail.comReceived on Mon May 31 2010 - 21:06:04 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:04 UTC