unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: "Schaefer, Frank" <frank.schaefer@tekcomms.com>
To: 20567@debbugs.gnu.org
Subject: bug#20567: guile 2.0.11 - test failures on mips64 big-endian with n32 ABI
Date: Wed, 13 May 2015 18:31:12 +0000	[thread overview]
Message-ID: <14E7D810D073F84195C3EE3EBF1E9C35746EB81C@US-PLNO-EXM01-P.global.tektronix.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1374 bytes --]

I've encountered two test failures with guile 2.0.11 on mips64 big-endian, whenever I build with -mabi=n32 (these test failures do not occur with -mabi=64).  At least one of them I have resolved with the attached patch.

First testcase failure: test-ffi (fixed by my patch).  The guile code apparently assumes that sizeof(ffi_arg)<=sizeof(void **).  This is a faulty assumption; it holds on *most* platforms, but with the mips64 n32 ABI, sizeof(void **)==4, and sizeof(ffi_arg)==8.  So every foreign function that returns a pointer is liable to corrupt data, and anyone retrieving the return value as a simple void * is only going to get sign-extension garbage on big-endian (usually NULL).

Second testcase failure: check-guile fails due to 'ERROR: foreign.test: procedure->pointer: qsort - arguments: ((null-pointer-error "pointer->bytevector" "null pointer dereference" () ()))'.  I strongly suspect it's related to the ffi_arg issue mentioned above, but I'm still peeling away macro ugliness to track it down.  If anyone wants to pitch in with additional guidance or patchwork, I'd be happy to listen and test.

(The patch applies against 2.0.11 release or against current HEAD, where it also fixes the new testcases for test-foreign-object-scm and test-foreign-object-c.  HEAD also fails the test-out-of-memory case, though, which precludes further unit tests.)

[-- Attachment #2: 0001-use-ffi_arg-instead-of-void-to-hold-FFI-call-return-.patch --]
[-- Type: application/octet-stream, Size: 1414 bytes --]

From 78ca71b314f4ad62d39d9acc53fabf0c41fa7521 Mon Sep 17 00:00:00 2001
From: Frank Schaefer <frank.schaefer@tekcomms.com>
Date: Wed, 13 May 2015 17:49:29 +0000
Subject: [PATCH] use ffi_arg instead of void * to hold FFI call return values

---
 libguile/foreign.c | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/libguile/foreign.c b/libguile/foreign.c
index 0cab6b8..5179d8e 100644
--- a/libguile/foreign.c
+++ b/libguile/foreign.c
@@ -26,6 +26,7 @@
 #include <alignof.h>
 #include <string.h>
 #include <assert.h>
+#include <stdint.h>
 
 #include "libguile/_scm.h"
 #include "libguile/bytevectors.h"
@@ -969,7 +970,7 @@ pack (const ffi_type * type, const void *loc, int return_value_p)
 	return scm_from_pointer (mem, NULL);
       }
     case FFI_TYPE_POINTER:
-      return scm_from_pointer (*(void **) loc, NULL);
+      return scm_from_pointer ((void *)(intptr_t)(*(ffi_arg *) loc), NULL);
     default:
       abort ();
     }
@@ -1003,7 +1004,7 @@ scm_i_foreign_call (SCM foreign, const SCM *argv)
     arg_size += cif->arg_types[i]->size + cif->arg_types[i]->alignment - 1;
 
   /* Space for argument values, followed by return value.  */
-  data = alloca (arg_size + cif->rtype->size
+  data = alloca (arg_size + max (sizeof(ffi_arg), cif->rtype->size)
 		 + max (sizeof (void *), cif->rtype->alignment));
 
   /* Unpack ARGV to native values, setting ARGV pointers.  */
-- 
2.3.1


             reply	other threads:[~2015-05-13 18:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-13 18:31 Schaefer, Frank [this message]
2016-06-24  5:17 ` bug#20567: guile 2.0.11 - test failures on mips64 big-endian with n32 ABI Andy Wingo

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

  List information: https://www.gnu.org/software/guile/

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

  git send-email \
    --in-reply-to=14E7D810D073F84195C3EE3EBF1E9C35746EB81C@US-PLNO-EXM01-P.global.tektronix.net \
    --to=frank.schaefer@tekcomms.com \
    --cc=20567@debbugs.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).