public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gcc-bugzilla at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/11410] New: ffitest failures on Solaris 8/SPARC
Date: Wed, 02 Jul 2003 18:21:00 -0000	[thread overview]
Message-ID: <20030702182116.11410.ro@techfak.uni-bielefeld.de> (raw)

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11410

           Summary: ffitest failures on Solaris 8/SPARC
           Product: gcc
           Version: 3.4
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: ro at techfak dot uni-bielefeld dot de
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: sparc-sun-solaris2.8
  GCC host triplet: sparc-sun-solaris2.8
GCC target triplet: sparc-sun-solaris2.8

The libffi test ffitest fails for both 32-bit and 64-bit (sparcv9):

in sparc-sun-solaris2.8/libffi, run

LD_LIBRARY_PATH=../../gcc ./ffitest

The test ends with

Enter FFI_CLOSURES

1 2 3 4 127 429 7 8 9 10 11 12 13 19 21 1 3: 680
Bus Error

In gdb, you find

Program received signal SIGSEGV, Segmentation fault.
0x00011364 in closure_test_fn1 (cif=0xffbee864, resp=0xffbee7f8, 
    args=0xffbee748, userdata=0x3)
    at /vol/gnu/src/gcc/gcc-dist/libffi/src/ffitest.c:325
1: x/i $pc  0x11364 <closure_test_fn1+156>:	ldd  [ %i0 ], %f8

%i0 (= cif) is not properly aligned for an 8-byte value, as can be observed
using truss:

9025:       Incurred fault #5, FLTACCESS  %pc = 0x00011364
9025:         siginfo: SIGBUS BUS_ADRALN addr=0xFFBEE8EC
9025:       Received signal #10, SIGBUS [default]
9025:         siginfo: SIGBUS BUS_ADRALN addr=0xFFBEE8EC
9025:           *** process killed ***

The SPARC-V9 test also fails, though in a different way:

in sparc-sun-solaris2.8/sparcv9/libffi, run

LD_LIBRARY_PATH=../../../gcc/sparcv9 ./ffitest

The test ends with

Enter FFI_CLOSURES

1 2 3 4 127 429 7 8 -2147483648 10 11 2147483647 13 19 21 1 3: 658
Test failure: /vol/gnu/src/gcc/gcc-dist/libffi/src/ffitest.c line 1203

If you disable the exit(EXIT_FAILURE) in ffitest.c (fail), the test finds
yet more errors:

1 2 3 4 127 429 7 8 -2147483648 10 11 2147483647 13 19 21 1 3: 658
Test failure: /vol/gnu/src/gcc/gcc-dist/libffi/src/ffitest.c line 1203
1 2 3 4 127 5 0 8 -2147483648 10 11 2147483647 13 19 21 1 3: 227
Test failure: /vol/gnu/src/gcc/gcc-dist/libffi/src/ffitest.c line 1235
1 2 3 4 127 5 0 8 -2147483648 10 11 2147483647 13 0 21 1 3: 208
Test failure: /vol/gnu/src/gcc/gcc-dist/libffi/src/ffitest.c line 1267
1 2 3 4 5 6 0 0 -2147483648 10 0 2147483647 13 0 0 1 3: 47
Test failure: /vol/gnu/src/gcc/gcc-dist/libffi/src/ffitest.c line 1300

Environment:
System: SunOS tikal 5.8 Generic_108528-19 sun4u sparc SUNW,Sun-Blade-1000
Architecture: sun4

	
host: sparc-sun-solaris2.8
build: sparc-sun-solaris2.8
target: sparc-sun-solaris2.8
configured with: /vol/gnu/src/gcc/gcc-dist/configure --prefix=/vol/gcc --with-local-prefix=/vol/gcc --disable-nls

How-To-Repeat:
Run ffitest as described above.


             reply	other threads:[~2003-07-02 18:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-02 18:21 gcc-bugzilla at gcc dot gnu dot org [this message]
2003-07-24  5:49 ` [Bug target/11410] " andreast at gcc dot gnu dot org
2003-07-29  4:49 ` pinskia at physics dot uc dot edu
2003-07-29  5:11 ` andreast at gcc dot gnu dot org
2003-07-30  4:04 ` cvs-commit at gcc dot gnu dot org
2004-01-11  1:36 ` [Bug libgcj/11410] " pinskia at gcc dot gnu dot org
2004-01-25  7:24 ` ebotcazou at gcc dot gnu dot org
2004-01-25  7:26 ` pinskia at gcc dot gnu dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030702182116.11410.ro@techfak.uni-bielefeld.de \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).