SUPERH platform development
 help / color / mirror / Atom feed
From: Rich Felker <dalias@libc.org>
To: linux-sh@vger.kernel.org
Subject: Re: SH2 kernel fails to build with recent GCC
Date: Wed, 12 Aug 2015 14:01:49 +0000	[thread overview]
Message-ID: <20150812140149.GA31018@brightrain.aerifal.cx> (raw)
In-Reply-To: <20150812015616.GA19843@brightrain.aerifal.cx>

On Wed, Aug 12, 2015 at 09:34:32AM +0200, Geert Uytterhoeven wrote:
> Hi Rich,
> 
> On Wed, Aug 12, 2015 at 3:56 AM, Rich Felker <dalias@libc.org> wrote:
> > The commit that resolved GCC issue #54089 broke building the kernel
> > for SH2, by causing GCC to generate calls to new libgcc functions
> > which the kernel's fake libgcc does not provide. See the GCC issue
> > tracker for details:
> >
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?idT089
> >
> > The relevant commit is linked from comment 16; comments 33-43 (and
> > perhaps beyond) discuss the issue in detail and possible fixes.
> >
> > Before I work on a fix, would dropping the kernel's copy of libgcc
> > functions for SH and using the real libgcc (like some archs do; see
> > comment 43) be acceptable, or do we need to get updated
> > libgcc[-compatible] code into the kernel?
> 
> Which libgcc functions are missing? I couldn't find that list in the bug
> report...

At least __ashlsi3_r0 and __lshrsi3_r0. It's been a while since I
tried building with an affected GCC (see the dates on the comments I
linked) so I don't remember if there were any others. I can try to
build again and let you know.

Rich

  parent reply	other threads:[~2015-08-12 14:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-12  1:56 SH2 kernel fails to build with recent GCC Rich Felker
2015-08-12  7:34 ` Geert Uytterhoeven
2015-08-12 14:01 ` Rich Felker [this message]
2015-08-14  1:10 ` Rich Felker

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=20150812140149.GA31018@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=linux-sh@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