On 07/03/2014 07:11 PM, Marek Polacek wrote:
On Thu, Jul 03, 2014 at 07:06:29PM +0200, Toon Moene wrote:
Compiler version: 4.10.0 20140702 (experimental) (GCC)
Platform: x86_64-unknown-linux-gnu
configure flags: --prefix=/home/toon/compilers/install --with-gnu-as
--with-gnu-ld --with-build-config=bootstrap-ubsan --enable-languages=all
--disable-multilib --disable-nls --with-arch=core-avx2 --with-tune=core-avx2
Note: --with-build-config=bootstrap-ubsan
Apparently, the bugs went wild ...
I suspect that's because:
https://gcc.gnu.org/ml/gcc-patches/2014-06/msg01549.html
which will go away if/when we fix:
https://gcc.gnu.org/ml/gcc-patches/2014-06/msg01624.html
But I'm only guessing.
Thanks - we will see. This is the schedule of test runs here at home:
"branch" boot-config languages
$ crontab -l
45 00 * * 0 $HOME/BootstrapGCC trunk lto all
45 00 * * 1 $HOME/BootstrapGCC fortran-dev lto fortran
45 00 * * 2 $HOME/BootstrapGCC trunk "asan --disable-werror" all
45 00 * * 3 $HOME/BootstrapGCC fortran-dev "asan --disable-werror" fortran
45 00 * * 4 $HOME/BootstrapGCC trunk ubsan all
45 00 * * 5 $HOME/BootstrapGCC fortran-dev ubsan fortran
45 00 * * 6 $HOME/BootstrapGCC trunk ubsan fortran
So the next test with bootstrap-config=ubsan is on Saturday, at 00:45
CEST - see if your fix can beat that :-)
Kind regards, and thanks for the explanation ...
--
Toon Moene - e-mail: t...@moene.org - phone: +31 346 214290
Saturnushof 14, 3738 XG Maartensdijk, The Netherlands
At home: http://moene.org/~toon/; weather: http://moene.org/~hirlam/
Progress of GNU Fortran: http://gcc.gnu.org/wiki/GFortran#news
