From mdowle at mdowle.plus.com  Sat Sep 27 17:59:09 2014
From: mdowle at mdowle.plus.com (Matt Dowle)
Date: Sat, 27 Sep 2014 16:59:09 +0100
Subject: [Rd] possible error in rdevel with --enable-strict-barrier?
Message-ID: <5426DECD.8060906@mdowle.plus.com>

Hi,

With a fresh Rdevel r66690 (yesterday 26th) in ~/R/Rtrunk I get :

~/R/Rtrunk $ ./configure CC="gcc -std=gnu99 -fsanitize=address" 
CFLAGS="-fno-omit-frame-pointer -O0 -g -Wall -pedantic -mtune=native" 
--without-recommended-packages
~/R/Rtrunk $ make clean
~/R/Rtrunk $ make

Works fine.

Now adding --enable-strict-barrier to the end :

~/R/Rtrunk $ ./configure CC="gcc -std=gnu99 -fsanitize=address" 
CFLAGS="-fno-omit-frame-pointer -O0 -g -Wall -pedantic -mtune=native" 
--without-recommended-packages --enable-strict-barrier
~/R/Rtrunk $ make clean
~/R/Rtrunk $ make
... snip ...
building package 'datasets'
make[4]: Entering directory `/home/mdowle/R/Rtrunk/src/library/datasets'
make[4]: Leaving directory `/home/mdowle/R/Rtrunk/src/library/datasets'
Error in stats::ts(t(matrix(data = c(1628.75, 1678.1, 1772.8, 2443.6,  :
   invalid time series parameters specified
Calls: <Anonymous> ... <Anonymous> -> sys.source -> eval -> eval -> 
<Anonymous>
Execution halted

I've done this with and without --enable-strict-barrier several times 
and it's repeatable, at least on my machine.

Am I doing it right?  Is it known?

~/R/Rtrunk $ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.8/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 4.8.2-1' 
--with-bugurl=file:///usr/share/doc/gcc-4.8/README.Bugs 
--enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr 
--program-suffix=-4.8 --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--with-gxx-include-dir=/usr/include/c++/4.8 --libdir=/usr/lib 
--enable-nls --with-sysroot=/ --enable-clocale=gnu 
--enable-libstdcxx-debug --enable-libstdcxx-time=yes 
--enable-gnu-unique-object --enable-plugin --with-system-zlib 
--disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo 
--with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.8-amd64/jre 
--enable-java-home 
--with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.8-amd64 
--with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.8-amd64 
--with-arch-directory=amd64 
--with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-objc-gc 
--enable-multiarch --with-arch-32=i586 --with-abi=m64 
--with-multilib-list=m32,m64,mx32 --with-tune=generic 
--enable-checking=release --build=x86_64-linux-gnu 
--host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 4.8.2 (Debian 4.8.2-1)

I should mention that I've also installed gcc 4.9.1 to try combining 
ASAN and UBSAN i.e. -fsanitize=undefined,address.  So it's possible that 
something in that install has upgraded a shared object somewhere else.  
In the command above I'm using just "gcc" in CC, though, not "gcc-4.9".  
The earlier snipped output confirms it is using gcc 4.8.2.

Anyway, posting here to see if it's just me or if there's really a minor 
issue with Rdevel currently.

Thanks,
Matt



[Rd] possible error in rdevel with --enable-strict-barrier?
Matt Dowle