public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Bastian Blank <waldi@debian.org>
To: linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org
Subject: [RFC][PATCH 0/5] Add and use libgcc
Date: Fri, 3 Apr 2009 17:39:41 +0200	[thread overview]
Message-ID: <20090403153941.GA7045@wavehammer.waldi.eu.org> (raw)

Hi

gcc always expects to be able to use the symbols in libgcc for
operations that are unsupported on the CPU.  Linux added functions if
needed or just worked around such operations.  Sometimes it even
describes the compiler as broken, even if it is properly documented by
gcc themself.

This patchset adds a copy of libgcc to the kernel and uses it if to do
such unsupported operations.  This way we can remove the usage of
workarounds like do_div.

Unsolved problems:
- It currently uses the gcc-included longlong division support which is marked
  as possibly trapping.
- The libgcc sources are currently unmodifed copies from gcc, this means
  it needs some headers with fixed names.

Bastian

-- 
Leave bigotry in your quarters; there's no room for it on the bridge.
		-- Kirk, "Balance of Terror", stardate 1709.2

             reply	other threads:[~2009-04-03 15:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-03 15:39 Bastian Blank [this message]
2009-04-03 15:40 ` [RFC][PATCH 0/5] Add and use libgcc Bastian Blank
2009-04-03 15:41 ` [PATCH 2/5] libgcc: Add config and support headers Bastian Blank
2009-04-03 15:41 ` [PATCH 3/5] libgcc: Add Makefile Bastian Blank
2009-04-03 15:42 ` [PATCH 4/5] libgcc: Disable usage of special do_div version Bastian Blank
2009-04-03 15:42 ` [PATCH 5/5] s390: Use libgcc Bastian Blank

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=20090403153941.GA7045@wavehammer.waldi.eu.org \
    --to=waldi@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox