search for: pr6616

...> compilers so this should be possible without too much trouble. > > I am working on such a recipe for testing 32 bit dragonegg, but so far it > fails mysteriously and I didn't figure it out yet. Great! It strikes me that we also have an issue with gcc version. As demonstrated by PR6616, compiler versions matter. It seems we will need to settle on a standard compiler for each release to avoid some of the confusion that can delay releases. What do the buildbots use? Unfortunately, this again makes things more complicated as it requires testers to install specific versions of com...

...ra 12, created a virtual machine by following the on-screen directions, and installing from a Debian 32-bit .iso. It couldn't have been simpler without someone else actually using the mouse for me. :-) > It strikes me that we also have an issue with gcc version. As demonstrated > by PR6616, compiler versions matter. It seems we will need to settle on a > standard compiler for each release to avoid some of the confusion that can > delay releases. What do the buildbots use? Unfortunately, this again makes > things more complicated as it requires testers to install specific...

...r are you using? I had a heck of a time setting up virt-manager. Perhaps Fedora does a better job integrating it than Debian. It wouldn't surprise me. I'm glad it's easy somewhere. :) > > It strikes me that we also have an issue with gcc version. As > > demonstrated by PR6616, compiler versions matter. It seems we will need > > to settle on a standard compiler for each release to avoid some of the > > confusion that can delay releases. What do the buildbots use? > > Unfortunately, this again makes things more complicated as it requires > > tes...

Hi David, > The second problem is the lack of x86-32 testing on Linux. This is only > going to get worse as x86-32 desktops and servers continue to disappear. this is not really a problem if you have root access on an x86-64 box. It is quite easy to install a 32 bit chroot environment. That's what I'm using on my laptop for testing x86-32. You really can't tell it's not

There was a short discussion in the comments of PR6696 about Linux testing. The 2.7 release is slipping primarily because there are x86-32 problems to fix (there is also a Darwin problem and some other issues). We have two problems with our testing: The OSU/Google buildbots aren't running test-suite, apparently. I didn't realize that and as this is the public testing face for LLVM, I