Bug#798111: Illegal instruction after compiling some code

2016-10-20 Thread Daniel Stender
Another case might be AFL:
https://bugs.debian.org/841474 afl: FTBFS on armhf (illegal instruction on 
test-instr.c)

DS

-- 
4096R/DF5182C8
http://www.danielstender.com/blog/



Bug#798111: Illegal instruction after compiling some code

2016-09-04 Thread Sylvestre Ledru

tag 798111 moreinfo
thanks


Le 05/09/2015 à 20:55, Julien Puydt a écrit :

Package: clang-3.8
Version: 1:3.8.0~svn245286-1

I tried to compile flint 2.5.2 (http://flintlib.org -- or the orig sources of 
experimental's flint package) with this version of clang to check if a problem 
I had with gcc 5 was compiler-related, but it gave me other problems : it 
compiled the lib and some tests ok, but when trying to actually run
those tests, I had failures "Illegal instruction".

Using clang version 3.5.2-2 (tags/RELEASE_352/final) (based on LLVM 3.5.2) gave 
the same result, but I prefer reporting on the last version.

I configured the sources like this:
CC=clang-3.8 ./configure --prefix=/usr --with-ntl CFLAGS='-D_FORTIFY_SOURCE=2 
-g -O2 -fstack-protector-strong -Wformat -Werror=format-security'
Sorry but I will  need more information to be able to anything here...

A test case would be the best.

Thanks
S



Bug#798111: Illegal instruction after compiling some code

2015-09-05 Thread Julien Puydt

Package: clang-3.8
Version: 1:3.8.0~svn245286-1

I tried to compile flint 2.5.2 (http://flintlib.org -- or the orig 
sources of experimental's flint package) with this version of clang to 
check if a problem I had with gcc 5 was compiler-related, but it gave me 
other problems : it compiled the lib and some tests ok, but when trying 
to actually run those tests, I had failures "Illegal instruction".


Using clang version 3.5.2-2 (tags/RELEASE_352/final) (based on LLVM 
3.5.2) gave the same result, but I prefer reporting on the last version.


I configured the sources like this:
CC=clang-3.8 ./configure --prefix=/usr --with-ntl 
CFLAGS='-D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security'


I hope it helps,

Snark on #debian-science