On 2 March 2011 02:34, Matthias Klose wrote:
> armel (although optimized for a different processor)
Hi
For which processor (/architecture) is it optimized, and do you mean
optimized-for, or only-runs-on?
I ask in case this would mean dumping all the armv4t systems that are
using Debian armel.
A patch has turned up for glibc-2.9. I'm trying it on eglibc-2.10...
See http://sourceware.org/ml/crossgcc/2009-11/msg8.html
--- glibc-ports-2.9/sysdeps/arm/dl-machine.h.orig 2009-11-03
22:03:57.0 +0100
+++ glibc-ports-2.9/sysdeps/arm/dl-machine.h2009-11-03 22:11:45.0
Confirmed - there is a misaligned word access in the test case
# echo 5 > /proc/cpu/alignnment
$ gcc foo.c
$ ./a.out
Bus error
reproducible in arm-sid using old-abi or eabi-oldabi-compat kernels.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [
On 6/24/08, Matthias Klose <[EMAIL PROTECTED]> wrote:
> Is this arm only, or armel as well?
armel too.
I have /proc/cpu/alignment set to 5 and it's doing an unaligned word access
under gdb (and gcc -g):
Program received signal SIGBUS, Bus error.
0x400d2cd0 in std::string::assign () from /usr/li
On 4/4/08, Matthias Klose <[EMAIL PROTECTED]> wrote:
> Martin Guy writes:
> > ...and on i386-sid on Athlon-32 the testsuite fails mightily:
> >
> > === libffi Summary ===
> >
> > # of expected passes505
> > # of unexpe
...and on i386-sid on Athlon-32 the testsuite fails mightily:
=== libffi Summary ===
# of expected passes505
# of unexpected failures513
# of unresolved testcases 8
# of unsupported tests 15
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with
Package: libffi
Version: 3.0.4-2
There are testsuite failures when building on ARM (which are then ignored...)
Running /home/martin/arm/arma/libffi-3.0.4/testsuite/libffi.call/call.exp ...
FAIL: libffi.call/cls_2byte.c -O0 -W -Wall execution test
FAIL: libffi.call/cls_3_1byte.c -O0 -W -Wall execu
I just tried foo.c on up-to-date arm-sid and armel-sid systems, both
under qemu and on real hardware and I cannot reproduce the problem;
all succeed the same way, for example:
[EMAIL PROTECTED]:~$ /usr/bin/gcc-4.2 foo.c
[EMAIL PROTECTED]:~$ ./a.out
0xbe92ec84
0x1
0x2
0x3
[EMAIL PROTECTED]:~$ gcc -
Package: gcc
Version: 4.1.1-13 (gcc version 4.1.2)
I was about to report the dangling symlinks in the gcc man directory
/usr/share/man/man1/i486-linux-gnu-cpp.1.gz -> cpp-4.1.1.gz
/usr/share/man/man1/cpp.1.gz -> cpp-4.1.1.gz
/usr/share/man/man1/c++.1.gz -> /etc/alternatives/c++.1.gz
/usr/share/ma
9 matches
Mail list logo
