Alpha arch development list
 help / color / mirror / Atom feed
From: Michael Cree <mcree@orcon.net.nz>
To: Bob Tracy <rct@gherkin.frus.com>
Cc: debian-alpha@lists.debian.org, linux-alpha@vger.kernel.org
Subject: Re: firefox-esr 52.6.0 available for alpha
Date: Wed, 28 Feb 2018 21:33:26 +1300	[thread overview]
Message-ID: <20180228083326.hh6yj2io4srbt34x@tower> (raw)
In-Reply-To: <20180228064354.GA28665@gherkin.frus.com>

On Wed, Feb 28, 2018 at 12:43:54AM -0600, Bob Tracy wrote:
> At some point in the near future, it will no longer be possible to build
> Firefox on an Alpha unless someone takes up the gauntlet and puts
> together a working Rust compiler. 

Rust uses the LLVM backend.  There was once an experimental Alpha
backend to LLVM.  I am currently attempting to forward port it to
more recent LLVM to see if it might be useful.  It only supported
EV6 and better CPUs which is a higher CPU standard than in Debian
Alpha.  I might get it back to EV56 (when BWX was introduced) and
be able to make sub-architectures to optionally switch in MVI and
CIX. But I have no intention of supporting anything without the
BWX.  And I doubt it will ever produce code the quality of gcc.

I do have a patch that would switch the Debian gcc to produce
code, by default, with BWX.  I haven't ever got around to sending
it to the gcc maintainer to switch over Debian Alpha to only
support Alphas with BWX.  But if I did that then if we ever got
LLVM going again on Alpha there would be no baseline
incompatibility.

Cheers
Michael.


      reply	other threads:[~2018-02-28  8:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-28  6:43 firefox-esr 52.6.0 available for alpha Bob Tracy
2018-02-28  8:33 ` Michael Cree [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=20180228083326.hh6yj2io4srbt34x@tower \
    --to=mcree@orcon.net.nz \
    --cc=debian-alpha@lists.debian.org \
    --cc=linux-alpha@vger.kernel.org \
    --cc=rct@gherkin.frus.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