public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Matthias Klose <doko@net.local> To: gcc-gnats@gcc.gnu.org, debian-gcc@lists.debian.org Subject: libgcj/10610: [powerpc-linux] 230 testsuite failures due to alignment errors Date: Sat, 03 May 2003 07:06:00 -0000 [thread overview] Message-ID: <E19Br5O-0007xS-00@tango.net.local> (raw) >Number: 10610 >Category: libgcj >Synopsis: [powerpc-linux] 230 testsuite failures due to alignment errors >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: wrong-code >Submitter-Id: net >Arrival-Date: Sat May 03 07:06:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: Matthias Klose >Release: 3.3 20030429 (Debian prerelease) (Debian testing/unstable) >Organization: >Environment: >Description: Seeing these failures only, when libffi is built with --enable-debug, on powerpc-linux only. The bugs remain without the --enable-debug switch, but are not triggered by the testsuite. All failures have the form ASSERTION FAILURE: ../../../src/libffi/src/powerpc/ffi.c line 118 Looking at libffi/include/ffi_common.h, the assertion triggers, if the macro argument is not properly aligned. ffi.c line 118: /* Check that everything starts aligned properly. */ FFI_ASSERT(((unsigned)(char *)stack & 0xF) == 0); The stack should be 16-byte aligned. Probably the wrong one of the multitude of stack alignment macros is being used. Appended is the test-summery of libjava configured with --enable-debug. === libjava tests === Running target unix FAIL: calls run FAIL: martin run FAIL: throwit run FAIL: ArrayStore execution - gij test FAIL: ArrayStore execution - gij test FAIL: ArrayStore2 execution - gij test FAIL: ArrayStore2 execution - gij test FAIL: Array_1 execution - gij test FAIL: Array_1 execution - gij test FAIL: Array_2 execution - gij test FAIL: Array_2 execution - gij test FAIL: Array_3 -O execution - source compiled test FAIL: Class_1 execution - gij test FAIL: Class_1 execution - gij test FAIL: Divide_1 execution - gij test FAIL: Divide_1 execution - gij test FAIL: Float_1 execution - gij test FAIL: Float_1 execution - gij test FAIL: G19990301_01 execution - gij test FAIL: G19990301_01 execution - gij test FAIL: G19990302_02 execution - gij test FAIL: G19990302_02 execution - gij test FAIL: G19990303_01 execution - gij test FAIL: G19990303_01 execution - gij test FAIL: G19990304_01 execution - gij test FAIL: G19990304_01 execution - gij test FAIL: G19990310_01 execution - gij test FAIL: G19990310_01 execution - gij test FAIL: II execution - gij test FAIL: II execution - gij test FAIL: InterfaceDispatch execution - gij test FAIL: InterfaceDispatch execution - gij test FAIL: InvokeReturn execution - source compiled test FAIL: InvokeReturn execution - gij test FAIL: InvokeReturn execution - bytecode->native test FAIL: InvokeReturn -O execution - source compiled test FAIL: InvokeReturn execution - gij test FAIL: InvokeReturn -O execution - bytecode->native test FAIL: Invoke_1 execution - gij test FAIL: Invoke_1 execution - gij test FAIL: Invoke_2 execution - gij test FAIL: Invoke_2 execution - gij test FAIL: KeepInline execution - gij test FAIL: KeepInline execution - gij test FAIL: Matrix4f execution - gij test FAIL: Matrix4f execution - gij test FAIL: N19990310_02 execution - gij test FAIL: N19990310_02 execution - gij test FAIL: N19990310_3 execution - gij test FAIL: N19990310_3 execution - gij test FAIL: N19990310_4 execution - gij test FAIL: N19990310_4 execution - gij test FAIL: N19990310_5 execution - gij test FAIL: N19990310_5 execution - gij test FAIL: PR141 execution - gij test FAIL: PR141 execution - gij test FAIL: PR160 execution - gij test FAIL: PR160 execution - gij test FAIL: PR162 execution - gij test FAIL: PR162 execution - gij test FAIL: PR218 execution - gij test FAIL: PR218 execution - gij test FAIL: PR242 execution - gij test FAIL: PR242 execution - gij test FAIL: PR260 execution - gij test FAIL: PR260 execution - gij test FAIL: PR3731 execution - gij test FAIL: PR3731 execution - gij test FAIL: PR5057 execution - gij test FAIL: PR5057 execution - gij test FAIL: PR5057_2 execution - gij test FAIL: PR5057_2 execution - gij test FAIL: PR6085 execution - gij test FAIL: PR6085 execution - gij test FAIL: PR6204 execution - gij test FAIL: PR6204 execution - gij test FAIL: PR6729 execution - gij test FAIL: PR6729 execution - gij test FAIL: Shazam execution - gij test FAIL: Shazam execution - gij test FAIL: StaticConstructor execution - gij test FAIL: StaticConstructor execution - gij test FAIL: StringBuffer_1 execution - gij test FAIL: StringBuffer_1 execution - gij test FAIL: SyncTest execution - gij test FAIL: SyncTest execution - gij test FAIL: Synch execution - gij test FAIL: Synch execution - gij test FAIL: TLtest execution - gij test FAIL: TLtest execution - gij test FAIL: TestProxy execution - source compiled test FAIL: TestProxy execution - gij test FAIL: TestProxy execution - bytecode->native test FAIL: TestProxy -O execution - source compiled test FAIL: TestProxy execution - gij test FAIL: TestProxy -O execution - bytecode->native test FAIL: Thread_Alive execution - gij test FAIL: Thread_Alive execution - gij test FAIL: Thread_Interrupt execution - gij test FAIL: Thread_Interrupt execution - gij test FAIL: Thread_Join execution - gij test FAIL: Thread_Join execution - gij test FAIL: Thread_Monitor execution - gij test FAIL: Thread_Monitor execution - gij test FAIL: Thread_Sleep execution - gij test FAIL: Thread_Sleep execution - gij test FAIL: Thread_Wait execution - gij test FAIL: Thread_Wait execution - gij test FAIL: Thread_Wait_2 execution - gij test FAIL: Thread_Wait_2 execution - gij test FAIL: Thread_Wait_Interrupt execution - gij test FAIL: Thread_Wait_Interrupt execution - gij test FAIL: Throw_2 execution - gij test FAIL: Throw_2 execution - gij test FAIL: anfi execution - gij test FAIL: anfi execution - gij test FAIL: anon execution - gij test FAIL: anon execution - gij test FAIL: anon2 execution - gij test FAIL: anon2 execution - gij test FAIL: anon3 execution - gij test FAIL: anon3 execution - gij test FAIL: anon4 execution - gij test FAIL: anon4 execution - gij test FAIL: anon_ctor_itf_arg execution - gij test FAIL: anon_ctor_itf_arg execution - gij test FAIL: anonarray execution - gij test FAIL: anonarray execution - gij test FAIL: anonarray2 execution - gij test FAIL: anonarray2 execution - gij test FAIL: direct_read execution - gij test FAIL: direct_read execution - gij test FAIL: direct_write execution - gij test FAIL: direct_write execution - gij test FAIL: err1 execution - gij test FAIL: err1 execution - gij test FAIL: err11 execution - gij test FAIL: err11 execution - gij test FAIL: err12 execution - gij test FAIL: err12 execution - gij test FAIL: err2 execution - gij test FAIL: err2 execution - gij test FAIL: err3 execution - gij test FAIL: err3 execution - gij test FAIL: err4 execution - gij test FAIL: err4 execution - gij test FAIL: err5 execution - gij test FAIL: err5 execution - gij test FAIL: err8 execution - gij test FAIL: err8 execution - gij test FAIL: err9 execution - gij test FAIL: err9 execution - gij test FAIL: final_inner execution - gij test FAIL: final_inner execution - gij test FAIL: final_int execution - gij test FAIL: final_int execution - gij test FAIL: final_static_and_friend execution - gij test FAIL: final_static_and_friend execution - gij test FAIL: indirect execution - gij test FAIL: indirect execution - gij test FAIL: indirect_read execution - gij test FAIL: indirect_read execution - gij test FAIL: indirect_write execution - gij test FAIL: indirect_write execution - gij test FAIL: initexc execution - gij test FAIL: initexc execution - gij test FAIL: initfield execution - gij test FAIL: initfield execution - gij test FAIL: inline execution - gij test FAIL: inline execution - gij test FAIL: inner1 execution - gij test FAIL: inner1 execution - gij test FAIL: inner2 execution - gij test FAIL: inner2 execution - gij test FAIL: inner3 execution - gij test FAIL: inner3 execution - gij test FAIL: inner4 execution - gij test FAIL: inner4 execution - gij test FAIL: inner_array execution - gij test FAIL: inner_array execution - gij test FAIL: inner_interface execution - gij test FAIL: inner_interface execution - gij test FAIL: instance execution - gij test FAIL: instance execution - gij test FAIL: instinit execution - gij test FAIL: instinit execution - gij test FAIL: instinit2 execution - gij test FAIL: instinit2 execution - gij test FAIL: invoke_from_inner execution - gij test FAIL: invoke_from_inner execution - gij test FAIL: invokethrow execution - gij test FAIL: invokethrow execution - gij test FAIL: klass execution - gij test FAIL: klass execution - gij test FAIL: multiple_finit execution - gij test FAIL: multiple_finit execution - gij test FAIL: nested_with_ctor execution - gij test FAIL: nested_with_ctor execution - gij test FAIL: override execution - gij test FAIL: override execution - gij test FAIL: pr133 execution - gij test FAIL: pr133 execution - gij test FAIL: pr179 execution - gij test FAIL: pr179 execution - gij test FAIL: pr6388 execution - gij test FAIL: pr6388 execution - gij test FAIL: pr83 execution - gij test FAIL: pr83 execution - gij test FAIL: pr8415 execution - gij test FAIL: pr8415 execution - gij test FAIL: pr8823 execution - gij test FAIL: pr8823 execution - gij test FAIL: pr8945 execution - gij test FAIL: pr8945 execution - gij test FAIL: private_direct_read execution - gij test FAIL: private_direct_read execution - gij test FAIL: search_outer execution - gij test FAIL: search_outer execution - gij test FAIL: stringconst execution - gij test FAIL: stringconst execution - gij test FAIL: stringconst2 execution - gij test FAIL: stringconst2 execution - gij test FAIL: stub execution - gij test FAIL: stub execution - gij test FAIL: test_long execution - gij test FAIL: test_long execution - gij test FAIL: tmi execution - gij test FAIL: tmi execution - gij test FAIL: tp execution - gij test FAIL: tp execution - gij test FAIL: update_outer execution - gij test FAIL: update_outer execution - gij test FAIL: utilTest execution - gij test FAIL: utilTest execution - gij test FAIL: /home/doko/3.3/gcc-3.3-3.3ds6/build/powerpc-linux/libjava/testsuite/TestEarlyGC.exe execution - /home/doko/3.3/gcc-3.3-3.3ds6/build/powerpc-linux/libjava/testsuite/TestEarlyGC.exe === libjava Summary === # of expected passes 2476 # of unexpected failures 235 # of expected failures 16 # of untested testcases 247 >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2003-05-03 7:06 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E19Br5O-0007xS-00@tango.net.local \ --to=doko@net.local \ --cc=debian-gcc@lists.debian.org \ --cc=gcc-gnats@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: linkBe 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).