mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
To: linux@roeck-us.net
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 17:49:49 +0200	[thread overview]
Message-ID: <201409151549.s8FFnner005703@ignucius.se.axis.com> (raw)
In-Reply-To: <20140915145203.GK4659@axis.com> (message from Jesper Nilsson on Mon, 15 Sep 2014 16:52:03 +0200)

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.

> I'm using gcc 4.7.2, but of course, that is a locally built
> version that might have patches not upstream
> (although I doubt it knowing the gcc CRIS maintainer :-)

(oops. *blush*)  The TLS stuff is unfortunately not upstreamed
at this time.  Unimportant when building the kernel, but
mentioned for completeness.  (The bad excuse is that I
originally awaited pre-v32 kernels to get the corresponding TLS
support so I wouldn't have to do ugly pre-vs.-v32 conditionals,
then the whole thing lost priority, and now I avoid adding code
I can't/won't test - the glibc end isn't upstreamed either.
Sorry.)

brgds, H-P

  reply	other threads:[~2014-09-15 15:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-31 17:50 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 [this message]
2014-09-15 18:30     ` Guenter Roeck
2014-09-16  3:22       ` Guenter Roeck
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=201409151549.s8FFnner005703@ignucius.se.axis.com \
    --to=hans-peter.nilsson@axis.com \
    --cc=edgar.iglesias@gmail.com \
    --cc=grant.likely@linaro.org \
    --cc=jespern@axis.com \
    --cc=linux-cris-kernel@axis.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    /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

Powered by JetHome