All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: sparclinux@vger.kernel.org
Subject: Debian drops support for sparc
Date: Thu, 30 Jul 2015 14:04:54 +0000	[thread overview]
Message-ID: <20150730140453.GA25014@ravnborg.org> (raw)

Hi all.

Debian have decided to drop support for sparc.
See additional details  here: https://lists.debian.org/debian-sparc/2015/07/msg00023.html

To the best of my understanding this is 32 bit userland
on top of sparc64 kernel that is dropped.

In Debian ports there is a sparc64 port which is 64-bit
userland on top of sparc64 kernel.
There are talks about improving support for the sparc64
ports but I have not read anything conclusive.

Additional details can be found the following bug report:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bugt5938

A major issue is that gcc-4.9 cannot be built for sparc
for reasons that I failed to follow.

When I read: https://bugs.debian.org/cgi-bin/bugreport.cgi?bugt5938#48
I get the impression that this is for the most part
bugs that may have been fixed recently.
The regression testing doen by Meelis Roos has shown
that things has improved a lot the last couple of months
if I recall correct. So sad that Debian drops sparc support now
when these fixes may not have propagated.

In a G+ post I also referred to the memcpy / FPU register
corruption bug that David only recently were able to reproduce.
I am not sure how much this bug influence the lack of stability
that people see when using sparc64 kernels.
See details here: http://marc.info/?t\x143382318800002&r=1&w=2

	Sam

             reply	other threads:[~2015-07-30 14:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-30 14:04 Sam Ravnborg [this message]
2015-07-30 15:36 ` Debian drops support for sparc Josip Rodin
2015-07-30 16:48 ` Sam Ravnborg
2015-07-30 17:31 ` Patrick Baggett
2015-07-30 18:11 ` David Miller
2015-07-30 19:22 ` Josip Rodin
2015-07-30 21:53 ` David Miller
2015-07-31  6:20 ` Kjetil Oftedal
2015-07-31  9:17 ` Josip Rodin
2015-07-31  9:20 ` Josip Rodin

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=20150730140453.GA25014@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=sparclinux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.