Hi Liu
> Chris is your boss? No. Who is Chris? > I know that EKOPath is much more better than open64, And could code of it useful for GCC or not? > but open64 can compile nothing but spec2000. Open64? I have googled at it. Do you mean that at http://www.open64.net/ I talked about Path64 https://github.com/path64 But you are right, at http://www.open64.net/about-open64.html there stand, that PathScale using it for EKOPath. And interestingly Open64 is a port of the old SGI-compiler. So Irix was written with MIPSPro and Open64 is a derivated work of it? Thats nice. > So, you want something about Effect, still? Yes. And I am looking, if there existing other OpenSource Compiler then GCC, which could be better in some areas. > GCC is the real compiler that can work! GCC can bootstrap, can compile > Linux Kernel, can compile GNU LibC, can compile almost everything. > Will open64? Does open64 really can be used? or just a tony with a > really suck codes? Why do you talk everytime about open64, when I talk about Path64? Open64 is the old one. I think if there existing nice code in it, GCC already have using it. Path64 is the new one, which opens. > GCC is the only choice in the real world except LLVM, but never open64. Can you descripe it a little bit more clear? What are the disadvantages of Open64 and what are the disadvantages of EKOPath/Path64? And if it have only disadvantages over GCC, why are people still working on Open64 and EKOPath/Path64? As I see, the newest version of Open64 was released April 13th, 2011. And EKOPath will now the times opened and becomes lot of updates. Open64 is under the GPL (similar to the GCC). But if GCC is the better one, why using PathScale for EKOPath and ENZO Open64 as base? But as I said before, it looks that PathScale using additional lot of parts of GCC: https://github.com/path64/compiler/tree/master/GCC https://github.com/path64/compiler/tree/master/gcc_incl Greatings theuserbl
