2011/6/18 theUser BL <theuse...@hotmail.com>: > > Hi! > > Currently I have nothing about it found in the mailinglist. So I try to ask > it: How effect the OpenSource EKOPath the GCC ? > > Have a look at the latest press news of PathScale: > http://www.pathscale.com/taxonomy/term/27 > > Have additional a look at this articls of phronix: > http://www.phoronix.com/scan.php?page=article&item=pathscale_ekopath4_open&num=1 > http://www.phoronix.com/scan.php?page=news_item&px=OTU2OA > > > The important things: > EKOPath will be step by step opend. First published opend code you can find at > https://github.com/path64 > > At > http://www.pathscale.com/ekopath-compiler-suite > you can download nightly builds. > To compile a helloworld.c program type > $ ~/ekopath-4.0.10/bin/pathcc helloworld.c -o helloworld > > You can use different benchmarks. For me it seems, that with EKOPath compiled > programs are a lot faster then with GCC. > > The only disadvantage is. that currently EKOPath exists only for 64bit > systems with x86_64 CPUs. > > But how will the OpenSource EKOPath effect GCC? > Can GCC make use of some EKOPath code? (EKOPath itself uses parts of GCC) > Or can GCC learn from it by studying it? > > Greatings > theuserbl > > >
Hi theuserbl Chris is your boss? I know that EKOPath is much more better than open64, but open64 can compile nothing but spec2000. So, you want something about Effect, still? 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? GCC is the only choice in the real world except LLVM, but never open64. --Liu
