public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "andreast at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgcj/10610] [powerpc-linux] 230 testsuite failures due to alignment errors Date: Fri, 24 Oct 2003 06:24:00 -0000 [thread overview] Message-ID: <20031024061614.21738.qmail@sources.redhat.com> (raw) In-Reply-To: <20030503070600.10610.doko@net.local> PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10610 ------- Additional Comments From andreast at gcc dot gnu dot org 2003-10-24 06:16 ------- The patchlet in the attachment does not help since it aligns the aligned bytes and not the so called misaligned stack. Here a snippet from gdb: Breakpoint 1, ffi_prep_args_SYSV (ecif=0x7ffff470, stack=0x7ffff428) at ../../../gcc/libffi/src/powerpc/ffi.c:126 126 FFI_ASSERT(((unsigned long)(char *)stack & 0xF) == 0); 1: x/i $pc 0xfcf5668 <ffi_prep_args_SYSV+152>: andi. r11,r4,15 Current language: auto; currently c (gdb) p ((unsigned long)(char *)stack & 0xF) == 0 $16 = 0 (gdb) p ((unsigned long)(char *)stack & 0x7) == 0 $18 = 1 So I'm investigating here....
next prev parent reply other threads:[~2003-10-24 6:16 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20030503070600.10610.doko@net.local> 2003-06-20 3:22 ` dhazeghi at yahoo dot com 2003-06-30 14:32 ` pinskia at physics dot uc dot edu 2003-10-23 20:41 ` andreast at gcc dot gnu dot org 2003-10-24 6:24 ` andreast at gcc dot gnu dot org [this message] 2003-10-28 19:46 ` cvs-commit at gcc dot gnu dot org 2003-10-28 20:24 ` cvs-commit at gcc dot gnu dot org 2003-10-28 21:15 ` cvs-commit at gcc dot gnu dot org 2003-10-28 22:10 ` cvs-commit at gcc dot gnu dot org 2003-10-30 5: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=20031024061614.21738.qmail@sources.redhat.com \ --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: 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).