search for: msg00888

FYI: http://gcc.gnu.org/ml/gcc/2005-11/msg00888.html It remains to be seen how well this will be accepted, but it gives some insight on what is being worked on. In any case, this probably won't have a large impact on the LLVM community, other than potentially more people working on it. -Chris -- http://nondot.org/sabre/ http://llvm.o...

...change the license to GPL? Also, would they be allergic to the VC++ suppport that currently exists? After all, if they're not careful, going down this route may result in a gcc that can be bootstrapped with VC++ :) Chris Lattner wrote: > > FYI: > http://gcc.gnu.org/ml/gcc/2005-11/msg00888.html > > It remains to be seen how well this will be accepted, but it gives > some insight on what is being worked on. In any case, this probably > won't have a large impact on the LLVM community, other than > potentially more people working on it. > > -Chris >

Chris Lattner wrote: > > FYI: > http://gcc.gnu.org/ml/gcc/2005-11/msg00888.html > > It remains to be seen how well this will be accepted, but it gives some > insight on what is being worked on. In any case, this probably won't > have a large impact on the LLVM community, other than potentially more > people working on it. Congratulations, i hope t...

...y result in a gcc > that can be bootstrapped with VC++ :) I don't think that's a problem. I think that, given a choice, allowing gcc to be bootstrapped with VC++ would be a favorable thing for the GCC community, regardless of LLVM. -Chris >> http://gcc.gnu.org/ml/gcc/2005-11/msg00888.html >> >> It remains to be seen how well this will be accepted, but it gives some >> insight on what is being worked on. In any case, this probably won't have >> a large impact on the LLVM community, other than potentially more people >> working on it. >&g...

On Tue, 22 Nov 2005, Marco Matthies wrote: > Chris Lattner wrote: >> FYI: >> http://gcc.gnu.org/ml/gcc/2005-11/msg00888.html >> >> It remains to be seen how well this will be accepted, but it gives some >> insight on what is being worked on. In any case, this probably won't have >> a large impact on the LLVM community, other than potentially more people >> working on it. > &...