Go compiler now committed to gcc mainline (to be gcc 4.6)
groups.google.com
Go compiler now committed to gcc mainline (to be gcc 4.6)
1–10 of 35 posts
Re: Go compiler now committed to gcc mainline (to be gcc 4.6)
#2So why didn't java and python made it to gcc ?
Re: Go compiler now committed to gcc mainline (to be gcc 4.6)
#3So why didn't java and python made it to gcc ?
[deleted]
Re: Go compiler now committed to gcc mainline (to be gcc 4.6)
#4So why didn't java and python made it to gcc ?
Because java did make it and python doesn't compile to machine code (with the exception of using a jit compiler maybe)?
Re: Go compiler now committed to gcc mainline (to be gcc 4.6)
#5So why didn't java and python made it to gcc ?
I'm trying to work out at what level your question makes sense. I'm unaware of a GCC-based Python compiler, so surely there's nothing to merge there?
As for Java: http://gcc.gnu.org/java/ (this has been in for years)
Re: Go compiler now committed to gcc mainline (to be gcc 4.6)
#6Anyone else has the problem that they need to log in with a Google account before being able to see posts on Google Groups? I even have this on the group I created, which I set to the most public settings.
Re: Go compiler now committed to gcc mainline (to be gcc 4.6)
#7More information here: http://www.airs.com/blog/archives/448
Re: Go compiler now committed to gcc mainline (to be gcc 4.6)
#8Anyone else has the problem that they need to log in with a Google account before being able to see posts on Google Groups? I even have this on the group I created, which I set to the most public settings.
Yes, I have noticed this. Although I am usually logged in to Google, it seems to want me to log in again, which I am much too lazy to do. So I just don't use Google Groups.
Re: Go compiler now committed to gcc mainline (to be gcc 4.6)
#9So why didn't java and python made it to gcc ?
What's gcj? Oh, the Java compiler in gcc? Hmm.
As for why Python isn't in gcc... it's because nobody has sent a patch. There is no conspiracy here; Google wrote Go and sent the gcc folks a patch to add it to gcc. Simple.
Re: Go compiler now committed to gcc mainline (to be gcc 4.6)
#10Why bother with GCC when the medium to long term seems to favor the LLVM compiler infrastructure? (and yes, I know you can use GCC together with LLVM, but for example, in Apple's case, XCode 4 now favors LLVM+Clang instead of the LLVM+GCC setup of XCode 3)