unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Andrew Pinski <pinskia-/MQLu3FmUzdAfugRpC6u6w@public.gmane.org>
To: rixed-ZMfTK6ahfJ9F0NgSq23LOA@public.gmane.org,
	loongson-dev-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org,
	guile-user-mXXj517/zsQ@public.gmane.org,
		libffi-discuss-R2MHTz/CkKAf7BdofF/totBPR1lH4CV8@public.gmane.org,
	green-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Subject: Re: Libffi (git master) and guile (git master) on MIPS n32
Date: Mon, 7 Feb 2011 13:58:07 -0800	[thread overview]
Message-ID: <AANLkTinKXwVL57k2KcBK6kVMDpQgLJODaPQXnHjpF1rg@mail.gmail.com> (raw)
In-Reply-To: <20110207214150.GA31804-Ir+b6ulHfbax5gEvnu9BZkTBJBY00kHK@public.gmane.org>

On Mon, Feb 7, 2011 at 1:41 PM,  <rixed-ZMfTK6ahfJ9F0NgSq23LOA@public.gmane.org> wrote:
> The problem is : of these 64 bits, only the 32 lowest bits were set by
> guile, and the upper 32 are desperately random.

How were those lower 32bits set?  If set by the 32bit instructions
then it is automatically sign extended.  If not then there is a bug in
how guile is doing the returns
Unless you have a bug somewhere in which you are using a non sign
extended value with the 32bit instructions which then it becomes
undefined at what the value of those instructions do (could be either
treating it as a 64bit value, or do a sign extend or even put
0xDEADBEEFDEADBEEF in the register which is what the Octeon simulators
do).

-- Pinski


  parent reply	other threads:[~2011-02-07 21:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-07 21:41 Libffi (git master) and guile (git master) on MIPS n32 rixed-ZMfTK6ahfJ9F0NgSq23LOA
     [not found] ` <20110207214150.GA31804-Ir+b6ulHfbax5gEvnu9BZkTBJBY00kHK@public.gmane.org>
2011-02-07 21:58   ` Andrew Pinski [this message]
     [not found]     ` <AANLkTinKXwVL57k2KcBK6kVMDpQgLJODaPQXnHjpF1rg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-02-08  7:48       ` rixed-ZMfTK6ahfJ9F0NgSq23LOA

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=AANLkTinKXwVL57k2KcBK6kVMDpQgLJODaPQXnHjpF1rg@mail.gmail.com \
    --to=pinskia-/mqlu3fmuzdafugrpc6u6w@public.gmane.org \
    --cc=green-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=guile-user-mXXj517/zsQ@public.gmane.org \
    --cc=libffi-discuss-R2MHTz/CkKAf7BdofF/totBPR1lH4CV8@public.gmane.org \
    --cc=loongson-dev-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    --cc=rixed-ZMfTK6ahfJ9F0NgSq23LOA@public.gmane.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).