unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@igalia.com>
To: William ML Leslie <william.leslie.ttg@gmail.com>
Cc: "debian-hppa@lists.debian.org" <debian-hppa@lists.debian.org>,
	Helge Deller <deller@gmx.de>,
	John David Anglin <dave.anglin@bell.net>,
	guile-devel@gnu.org,
	John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Subject: Re: Removal of hppa support
Date: Mon, 27 Jan 2020 16:46:32 +0100	[thread overview]
Message-ID: <87eevkgaw7.fsf@igalia.com> (raw)
In-Reply-To: <CAHgd1hGS-xXhiUzW540+9rse0VEwaTMwA33w-hjzTprnWccA5Q@mail.gmail.com> (William ML Leslie's message of "Sun, 26 Jan 2020 17:19:44 +1100")

Hi :)

On Sun 26 Jan 2020 07:19, William ML Leslie <william.leslie.ttg@gmail.com> writes:

> On Sun, 26 Jan 2020, 4:46 pm William ML Leslie, <william.leslie.ttg@gmail.com> wrote:
>  On Sun, 26 Jan 2020, 8:20 am John Paul Adrian Glaubitz, <glaubitz@physik.fu-berlin.de> wrote:
>
>  > I noticed that you recently purged hppa support from guile [1].
>
>  This change does not remove hppa support from guile, only support for
>  the jit.
>
>  As an ia64 user, i'm a bit sad that we lost jit too - but i don't run
>  any performance-sensitive guile jobs on that system.
>
> Maybe /lost/ is the wrong word. We won't be benefitting from the work
> the lightning team have done in supporting hacker-friendly
> architectures in guile 3. This jit is completely new.

William is correct.  HPPA support is not gone from Guile; and indeed
it's good to hear from you :)  I wasn't sure there were any IA64 users
remaining.

Initially in Guile I planned to use GNU Lightning, in part because of
its great platform support.  However it turned out to not be the right
thing, and reluctantly I ended up doing something that was more like a
rewrite than a refactor.  In that context I personally don't have the
budget to write the IA64 backend.  So, Guile 3 still runs on IA64, just
without JIT support.

If someone would like to write an IA64 backend for Lightening, I would
be happy to accept it :)  The beginnings of one are there in the git
history.

Andy



  reply	other threads:[~2020-01-27 15:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-25 19:32 Removal of hppa support John Paul Adrian Glaubitz
2020-01-25 19:48 ` John David Anglin
2020-01-25 21:59   ` Helge Deller
2020-01-26  5:46 ` William ML Leslie
2020-01-26  6:19   ` William ML Leslie
2020-01-27 15:46     ` Andy Wingo [this message]
2020-01-27 17:30       ` Stefan Monnier
2020-01-27 21:41         ` tomas
2020-02-04 11:02       ` John Paul Adrian Glaubitz
2020-02-04 11:23         ` Andy Wingo
2020-02-04 11:41           ` John Paul Adrian Glaubitz
2020-01-26  9:50   ` John Paul Adrian Glaubitz
2020-01-26 12:21     ` William ML Leslie
2020-01-26 13:34       ` John Paul Adrian Glaubitz
2020-01-26 15:50         ` John David Anglin

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=87eevkgaw7.fsf@igalia.com \
    --to=wingo@igalia.com \
    --cc=dave.anglin@bell.net \
    --cc=debian-hppa@lists.debian.org \
    --cc=deller@gmx.de \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=guile-devel@gnu.org \
    --cc=william.leslie.ttg@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).