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

> But I think the focus should probably be on the sheer redness of the sparc
> columns at:
> https://release.debian.org/jessie/arch_qualify.html (current release)

From the link above:
"
sparc

Upstream Support

According to the gcc maintainer 32bit code generation as we use it is no longer supported upstream and we should aim for a switch to 64bit userland anytime soon.
"

Is it correct that 32bit gcc is no longer maintained?
I have seen nothing on gcc mailaing list about this.

	Sam

  parent reply	other threads:[~2015-07-30 16:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-30 14:04 Debian drops support for sparc Sam Ravnborg
2015-07-30 15:36 ` Josip Rodin
2015-07-30 16:48 ` Sam Ravnborg [this message]
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=20150730164823.GA26679@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.