26.06.2012, 12:11, "Konstantin Tokarev" <[email protected]>: > 25.06.2012, 20:47, "John Regehr" <[email protected]>: > >>> For some cases it takes more than 1 day on powerful machine. >> Yes, this is pretty painful. I'm happy to work on optimizing things. I >> have various ideas that may be useful. >>> Unfortunately, this compiler is closed-source so you cannot build it. >>> Will it be enough if I provide you binaries? >> A binary compiler + a couple of testcases would be great. Can you give >> me something that runs on Ubuntu 10.04 or 12.04 for x86-64? If you are >> using some different Linux, linking statically or using CDE may be >> sufficient: >> >> http://www.pgbovine.net/cde.html >> >> I do not currently have a fast MacOS or Windows machine available. >> >> John > > You can start with test case from my "C++ test case" thread from 2nd June. > For convenience, I'll repeat instructions here. Initial translation unit is > attached. > > 1. Install nightly build of ENZO compiler: > wget > http://c591116.r16.cf2.rackcdn.com/enzo/nightly/Linux/enzo-2012-06-02-installer.run > > 2. Install it: > chmod +x enzo-2012-06-02-installer.run > /enzo-2012-06-02-installer.run --mode unattended # as root > > 3. test.sh > > #!/bin/sh > > FILE=GlobalOpt.cpp > PATHCC=/opt/enzo-4.9.00/bin/pathCC > GCC=clang++ > > $GCC -c $FILE -fsyntax-only -o /dev/null &> /dev/null && $PATHCC -c -o > /dev/null $FILE 2>&1 | \ > grep 'DOM_INFO::Build_pdom_tree: No post-dom for BB_NODE' \ > &> /dev/null
Note that 94% of this translation unit are standard headers which have much lower probability of triggering compiler bugs. -- Regards, Konstantin
