[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gentoo-dev
Subject:    [gentoo-dev] EKOPath/Path64 compiler ebuilds + support
From:       "C._Bergström" <cbergstrom () pathscale ! com>
Date:       2011-07-30 6:45:55
Message-ID: 4E33A8A3.5050809 () pathscale ! com
[Download RAW message or body]


Hi

Recently a couple new ebuilds were added to the portage tree and I felt 
it's worthwhile to give a friendly heads up.

So without further ado let me introduce EKOPath and Path64.

EKOPath - This is a binary installer that comes from one of the nightly 
PathScale builds.  The source to the compiler/debuger/libraries.. etc 
are available on github.  It's meant as a convenience to new users and 
should be portable across many distributions.

Path64 - This is the source build of the compiler that will warm your 
house in the winter.  While not required I would generally recommend 
that you do a Release build.  If you don't the compiler will be *slower* 
than mud.  It may not be so bad if you're not building any C++ code, but 
you've been warned.
-------------
Documentation - We're working on it, but help is appreciated.  
Converting a 300 page user guide from $proprietary discontinued format 
to latex isn't fun.  (Send me a private email if you're interested to help)

Support - Our mailing lists are quiet, but most questions will get a 
response
http://lists.pathscale.com/mailman/listinfo

If you're on irc feel free to say hi or ask questions on freenode - 
#pathscale
# Warning: The channel is generally quite friendly unless you say 
something stupid or piss off an OP
--------------

Bug reports
For now we're using github issues.  # Yes it sucks and we'll get a jira 
instance setup some time in the future
https://github.com/path64/compiler/issues/

We welcome any and all bug reports - performance regressions, ICE, 
incorrect results. etc.  The best way to get your bug fixed is by having 
the smallest possible test case which reproduces the problem.

We generally recommend the tool Delta for getting a good automatic start 
before hand reducing
http://delta.tigris.org/

Why care?
PathScale traditionally cared a lot about the performance for HPC and 
scientific codes.  If you have some Fortran code I'd highly recommend 
you give it a try.  C++ is getting a lot of improvements and we're 
aiming to take the lead before the end of the year.  That leaves C and 
anything else which people really care about
(OpenSSL, web servers, database.. etc)  Try to build it, file good bug 
reports, tweak the flags for best performance and yell at us if we're 
not the fastest.

I'm around if you have any questions or just generally need someone to 
yell at :)


./C

@CTOPathScale


[prev in list] [next in list] [prev in thread] [next in thread]