From: Eli Zaretskii <eliz@gnu.org>
To: ludo@gnu.org (Ludovic Courtès)
Cc: xdje42@gmail.com, gdb-patches@sourceware.org
Subject: Re: Building the current snapshot on Windows with Guile
Date: Thu, 12 Jun 2014 17:15:00 -0000 [thread overview]
Message-ID: <83sinaxd5s.fsf@gnu.org> (raw)
In-Reply-To: <87ha3qlehr.fsf@gnu.org>
> From: ludo@gnu.org (Ludovic Courtès)
> Cc: xdje42@gmail.com, gdb-patches@sourceware.org
> Date: Thu, 12 Jun 2014 10:27:12 +0200
>
> > Apart of the issue with multi-ABI platforms, are there any other
> > reasons for the *.go files to be non-portable?
>
> In Guile 2.0, .go files are not portable essentially because sizeof(SCM)
> is the size of a pointer, and because numbers stored in .go files are in
> native endianness. (Guile 2.2 uses ELF as its container format, with
> similar issues.)
Ouch! That's going to be a drag, IMO. Now I understand why there are
no compiled *.go files in the Guile distribution (unlike with Emacs,
for example).
In that case, I guess it will be impossible to distribute precompiled
scm files with the GDB tarball, per your suggestion. Or am I missing
something?
> > E.g., if they were compiled on a 64-bit Windows 7, will they work on a
> > 32-bit Windows XP?
>
> No.
>
> > Does the answer depend on whether the Guile executable that compiled
> > the *.scm files was a 64-bit or a 32-bit executable?
>
> No.
I'm puzzled: a 32-bit program still produces 32-bit code and uses
32-bit pointers, even when it runs on a 64-bit machine. So why the
second "No"?
> > What about compiling on GNU/Linux and using on Windows, when the CPU
> > is the same or from the same family?
>
> That works fine.
Do the .go files use portable format for numbers? There's a potential
issue because a 'long' on a 64-bit GNU/Linux system is a 64-bit
quantity, while 64-bit Windows uses 32-bit 'long's. Could this be an
issue?
Thanks.
next prev parent reply other threads:[~2014-06-12 17:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 15:24 Eli Zaretskii
2014-06-09 15:39 ` Joel Brobecker
2014-06-09 17:30 ` Eli Zaretskii
2014-06-14 18:01 ` Eli Zaretskii
2014-06-09 21:04 ` Ludovic Courtès
2014-06-10 19:55 ` Doug Evans
2014-06-10 20:26 ` Eli Zaretskii
2014-06-11 12:24 ` Ludovic Courtès
2014-06-11 14:59 ` Eli Zaretskii
2014-06-12 8:27 ` Ludovic Courtès
2014-06-12 17:15 ` Eli Zaretskii [this message]
2014-06-12 19:46 ` Ludovic Courtès
2014-06-12 19:58 ` Eli Zaretskii
2014-06-13 8:35 ` Ludovic Courtès
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=83sinaxd5s.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=ludo@gnu.org \
--cc=xdje42@gmail.com \
/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).