13 Jul
2013
13 Jul
'13
3:34 p.m.
On 13/07/13 17:40, Andreas Radke wrote:
Uploaded tarballs with gcc47 and 48 with -O0 and -save-temps:
https://docs.google.com/file/d/0B8HSjV2qdYV1VXhmdnlxc29RZDQ/edit?usp=sharing https://docs.google.com/file/d/0B8HSjV2qdYV1aE80NWh4S1Yzdlk/edit?usp=sharing
Feel free to run meld over .s files.
The first thing to be done is to limit the issue to a single file. I.e. which file do you need to compile with gcc-4.8 to generate the issue. You could also bisect gcc to find the broken commit. The gcc-git PKGBUILD in the AUR will bisect quite easily (add #commit=xxxxxx at the end of the source) if you uncomment the lines after the "XXX" markers. Building with --nocheck will not take too long to build. Allan