From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: guile-devel@gnu.org
Subject: Re: [Guile-commits] GNU Guile branch, stable-2.0, updated. v2.0.7-131-gb946e08
Date: Thu, 28 Feb 2013 12:02:12 +0100 [thread overview]
Message-ID: <87ppzkbt1n.fsf@gnu.org> (raw)
In-Reply-To: <87bob5xklz.fsf@tines.lan> (Mark H. Weaver's message of "Wed, 27 Feb 2013 21:01:12 -0500")
Hi Mark,
Mark H Weaver <mhw@netris.org> skribis:
> "Ludovic Courtès" <ludo@gnu.org> writes:
>> commit cc2948aa3189b7bd29c23e7a93ccb1217a1b4eff
>> Author: Ludovic Courtès <ludo@gnu.org>
>> Date: Wed Feb 27 20:07:12 2013 +0100
>>
>> Recognize mips64* as having 32-bit pointers by default.
>>
>> * module/system/base/target.scm (cpu-word-size): Consider MIPS64 to
>> default to n32 or o32.
> [...]
>
> This seems questionable to me. It may currently be the case that N32
> and O32 are more common, but that is unlikely to remain the case for
> much longer.
>
> Is there any way to specify the N64 ABI for MIPS?
There’s *-gnuabi64 as shown in one of these commits, though it’s up to
the tools to interpret it as we want (GCC, Binutils, Guile, etc.)
Currently, it seems that GCC & co. don’t support it (GCC has a
‘--with-abi’ configure flag.)
Ludo’.
prev parent reply other threads:[~2013-02-28 11:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1UAn2f-0008NQ-Lc@vcs.savannah.gnu.org>
2013-02-28 2:01 ` [Guile-commits] GNU Guile branch, stable-2.0, updated. v2.0.7-131-gb946e08 Mark H Weaver
2013-02-28 10:38 ` Mark H Weaver
2013-02-28 11:02 ` Ludovic Courtès [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
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=87ppzkbt1n.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
--cc=mhw@netris.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).