From: Efraim Flashner <efraim@flashner.co.il>
To: Simon South <simon@simonsouth.net>
Cc: 41648@debbugs.gnu.org
Subject: [bug#41648] [PATCH 0/2] JamVM: Add aarch64-linux support
Date: Tue, 2 Jun 2020 12:41:29 +0300 [thread overview]
Message-ID: <20200602094129.GK7397@E5400> (raw)
In-Reply-To: <20200601171211.7272-1-simon@simonsouth.net>
[-- Attachment #1: Type: text/plain, Size: 847 bytes --]
On Mon, Jun 01, 2020 at 01:12:11PM -0400, Simon South wrote:
>
> Note I have found it unnecessary to use older versions of gcc and glibc when
> building JamVM 1.5.1 on AArch64; the CPU's instruction cache is flushed
> explicitly on this platform so it shouldn't be possible for the "invalid
> instruction" situation mentioned in a comment to develop, and I haven't seen
> it myself.
>
Can you test running bootstrap on jamvm-1-bootstrap (and jamvm@2) and
see if that negates the need for an older version of glibc and gcc on
other platforms? (basically just x86_64 for now, unless it now works on
other architectures)
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-06-02 9:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-01 17:12 [bug#41648] [PATCH 0/2] JamVM: Add aarch64-linux support Simon South
2020-06-01 17:15 ` [bug#41648] [PATCH 1/2] gnu: jamvm-1-bootstrap: " Simon South
2020-06-01 17:15 ` [bug#41648] [PATCH 2/2] gnu: jamvm: " Simon South
2020-06-02 9:41 ` Efraim Flashner [this message]
2020-06-02 16:04 ` [bug#41648] [PATCH 0/2] JamVM: " Simon South
2020-06-02 18:35 ` Efraim Flashner
2020-06-15 13:56 ` Simon South
2020-06-25 10:30 ` Efraim Flashner
2020-06-28 7:48 ` bug#41648: " Efraim Flashner
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200602094129.GK7397@E5400 \
--to=efraim@flashner.co.il \
--cc=41648@debbugs.gnu.org \
--cc=simon@simonsouth.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).