From: Brian Mokrzycki <brian-mokrzycki@uiowa.edu>
To: cgen@sourceware.org
Subject: Re: 64-bit instruction mask emitting as signed hex value
Date: Wed, 05 Oct 2011 21:40:00 -0000 [thread overview]
Message-ID: <A6EE93A0-13FB-4B48-995B-CDDE32305C71@uiowa.edu> (raw)
In-Reply-To: <9453F244-7E2E-47CA-8789-9CAC7156A710@uiowa.edu>
OK, I only have a fuzzy feeling as to how I got this resolved. Basically I uninstalled guile from MacPorts and utilized a different portage system (homebrew) to reinstall guile 1.8.7.
During the reinstall homebrew was stating that guile 1.8.7 does not support compilation with LLVM and suggested I switch over to using GCC. So I did that and now I get the proper behavior
guile> (number->string 0xFFFFFFFFFFFFFFFF 16)
"ffffffffffffffff"
I can't be certain that there wasn't some underlying dependency that was compiled with different configure flags… but I can say "It works" and I can move on to the next issue.
If anyone wants to pipe in and give me a definitive answer I would appreciate it.
Thanks,
-Brian
On Oct 5, 2011, at 3:41 PM, Brian Mokrzycki wrote:
> Interesting. I'm running Guile 1.8.7 on Mac OS X Lion (10.7) and installed it with MacPorts, the Portfile for guile 1.8.7 at revision 2. I think the next step is to download the source directly from gnu and see if it was simply a compile option that was missed.
>
> And issuing the identical statement on my installation is
>
> guile> (number->string 18446744073709551615 16)
> "-1"
>
> Thanks for the additional clue.
>
> -Brian
>
> On Oct 5, 2011, at 3:34 PM, Frank Ch. Eigler wrote:
>
>> Hi -
>>
>> On Mon, Oct 03, 2011 at 09:57:39PM -0500, Brian Mokrzycki wrote:
>>> [...]
>>
>> Good hunting!
>>
>>> Guile 1.6.8
>>> guile> (number->string 0xFFFFFFFFFFFFFFFF 16)
>>> "ffffffffffffffff"
>>>
>>> Guile 1.8.7
>>> guile> (number->string 0xFFFFFFFFFFFFFFFF 16)
>>> "-1"
>>
>> In the case of guile 1.8.8 (fedora 15 x86_64),
>> and guile 1.8.0 (rhel5 i386),
>>
>> guile> (number->string 18446744073709551615 16)
>> "ffffffffffffffff"
>>
>> Maybe something's wrong just with your build of guile somehow.
>>
>> - FChE
>
prev parent reply other threads:[~2011-10-05 21:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-04 2:57 Brian Mokrzycki
2011-10-05 20:34 ` Frank Ch. Eigler
2011-10-05 20:41 ` Brian Mokrzycki
2011-10-05 21:40 ` Brian Mokrzycki [this message]
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=A6EE93A0-13FB-4B48-995B-CDDE32305C71@uiowa.edu \
--to=brian-mokrzycki@uiowa.edu \
--cc=cgen@sourceware.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).