- C++0x support will likely come to PathScale ENZO before it's introduced in the EKOPath compiler, due to different front-ends being used.
- EKOPath will hopefully be able to build the Qt tool-kit within the next month or so (there's one blocking bug at the moment).
- This EKOPath compiler just takes advantage of the CPU, not the GPU, like the PathScale ENZO product.
- One of our favorite comments by Bergström, "Binary size doesn't matter in reality as much as locality. C++ is going to see a lot of improvements this year. If we're not faster than g++ or other compilers file a bug report." (If only all Linux projects took performance this seriously...)
- Bergström's comments regarding Open64 vs. EKOPath relationship: "EKOPath is a 'fork' of SGI's Pro64 and never has imported code from Open64. Partial sources for EKOPath were previously available, but not all. Large portions of those sources were merged into Open64 as a result of previous PathScale management not supporting open source. Slowly the PathScale ship is changing direction and trying to build a real community of users/developers." Additionally, "1) We 'forked' pro64 like 8 year ago and import nothing from open64 2) Open64 imported heavily from PathScale tarballs that were released previously so in reality it's a fork from us! (Check their early commit logs to see what I mean) 3) More 'stuff' coming open source and will be available at our pathscale github account. Path64 won't get anymore sources directly added to it."
- Regarding whether some of the EKOPath performance optimizations could be ported to the GNU Compiler Collection: "Sure you can port optimizations, but not every ball of yarn is created equal. Compilers are generally speaking an extremely complicated piece of software and the effectiveness of optimizations can be dependent on many things. EKOPath has been engineered for performance and we're in a good position to stay ahead in areas we focus on."
- The Path64 GitHub source tree isn't the full source to EKOPath. All of the sources are still being opened up and should be pushed publicly within a few days.
- In terms of why PathDB (PathScale's debugger) was open-sourced: "Our goal for PathDB is/was to build an initial community of users inside the BSD community."
There's more comments by the PathScale and the Phoronix community in the forums.