From: Guenter Roeck <linux@roeck-us.net>
To: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
Cc: jespern@axis.com, linux-cris-kernel@axis.com,
linux-kernel@vger.kernel.org, grant.likely@linaro.org,
edgar.iglesias@gmail.com
Subject: Re: Status of 'cris' architecture support in Linux kernel
Date: Mon, 15 Sep 2014 20:22:12 -0700 [thread overview]
Message-ID: <20140916032212.GA7759@roeck-us.net> (raw)
In-Reply-To: <20140915183007.GA25962@roeck-us.net>
On Mon, Sep 15, 2014 at 11:30:07AM -0700, Guenter Roeck wrote:
> On Mon, Sep 15, 2014 at 05:49:49PM +0200, Hans-Peter Nilsson wrote:
> > Following up on Jesper's reply...
> >
> > > From: Jesper Nilsson <jespern@axis.com>
> > > Date: Mon, 15 Sep 2014 16:52:03 +0200
> >
> > > > Toolchain
> > > >
> > > > Creating a toolchain from upstream sources required a number of patches.
> >
> > > > - gcc 4.7.4
> > > > Requires a backport from upstream gcc to compile.
> > > > Later versions of gcc (4.8.3, 4.9.1) fail with internal compiler errors
> > > > even after patching.
> >
> > This sounds like PR61737 (fixed; use 4.9.2 not released yet),
> > but of course with the above sentence serving as your complete
> > bug-report (or did I miss one?) that will only be a guess.
> >
> Confirmed; gcc 4.9.1 for crisv32 builds after applying the patch fixing
> PR61737 (and the patch to fic config.gcc) on top of gcc 4.9.1.
>
Not-so-good update: I got the toolchain with gcc 4.9.1 to build,
but the resulting image hangs early during boot. This does not happen
if I use the toolchain with gcc 4.7.4. Guess I'll stick with that.
Guenter
next prev parent reply other threads:[~2014-09-16 3:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-31 17:50 Status of 'cris' architecture support in Linux kernel Guenter Roeck
2014-08-31 18:33 ` Sam Ravnborg
2014-08-31 18:49 ` Guenter Roeck
2014-09-01 3:49 ` Mikael Starvik
2014-09-15 14:52 ` Jesper Nilsson
2014-09-15 15:49 ` Hans-Peter Nilsson
2014-09-15 18:30 ` Guenter Roeck
2014-09-16 3:22 ` Guenter Roeck [this message]
2014-09-15 19:55 ` Guenter Roeck
2014-09-15 22:37 ` Edgar E. Iglesias
2014-09-16 7:23 ` Geert Uytterhoeven
2014-09-16 13:24 ` Guenter Roeck
2014-09-17 19:07 ` Guenter Roeck
2014-09-18 8:52 ` Jesper Nilsson
2014-09-21 16:47 ` Guenter Roeck
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=20140916032212.GA7759@roeck-us.net \
--to=linux@roeck-us.net \
--cc=edgar.iglesias@gmail.com \
--cc=grant.likely@linaro.org \
--cc=hans-peter.nilsson@axis.com \
--cc=jespern@axis.com \
--cc=linux-cris-kernel@axis.com \
--cc=linux-kernel@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.