search for: gcc63

...chitectures, misaligned loads/stores cause bus errors in Sparc. To catch bugs specific to Sparc such as the misalignment bugs, it would be great to get some buildbots running on Sparc machines. I see that there are buildbot slaves already running on Sparc machines in GCC compile farm (for example, gcc63, gcc64, listed at http://lab.llvm.org:8011/buildslaves). Is it possible to start running builders on them? If so, what are the procedures to do that? Note that clang still does not work when it is build as a 32-bit binary, mainly due to the alignment issues in Clang. Also, Clang does not work out...

...us errors in Sparc. >> >> To catch bugs specific to Sparc such as the misalignment bugs, it >> would be great to get some buildbots running on Sparc machines. I see >> that there are buildbot slaves already running on Sparc machines in >> GCC compile farm (for example, gcc63, gcc64, listed at >> http://lab.llvm.org:8011/buildslaves). Is it possible to start running >> builders on them? If so, what are the procedures to do that? >> >> Note that clang still does not work when it is build as a 32-bit >> binary, mainly due to the alignment is...

...They are currently idle because no builders have been scheduled to use them: # gcc54 36G 0.5 GHz TI UltraSparc IIe (Hummingbird) / 1.5 GB RAM / Sun Netra T1 200 / Debian sparc # gcc62 9202 36G 6x0.4 GHz TI UltraSparc II (BlackBird) / 5 GB RAM / Sun Enterprise 4500 / Debian sparc # gcc63 9203 72G 8x4x1 GHz Sun UltraSparc T1 (Niagara) / 8 GB RAM / Sun Fire T1000 / Debian sparc Feel free to use them. I can give you login access if you send me a public ssh key. Ciao, Duncan.

Chris, > FYI, I completely agree that we shouldn't remove the sparc target. However, it is currently unmaintained, and has some pretty glaring bugs. Is anyone interested in stepping up to maintain the target? > > -Chris We can not let it die and I volunteer to keep the Sparc alive! My SPARCstation pizzaboxes can be ready for action in a day or two. Pawel Wodnicki > On Oct