mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
To: xili_gchen_5257@hotmail.com
Cc: jespern@axis.com, starvik@axis.com, linux-kernel@vger.kernel.org,
	linux-cris-kernel@axis.com
Subject: Re: [Consult] cris: arch-v10: About $dtp0 register
Date: Wed, 5 Aug 2015 18:56:27 +0200	[thread overview]
Message-ID: <201508051656.t75GuRWq016534@ignucius.se.axis.com> (raw)
In-Reply-To: <BLU436-SMTP1822B5A35A31370E50E1BBDB9750@phx.gbl> (message from Chen Gang on Wed, 5 Aug 2015 16:39:00 +0200)

> From: Chen Gang <xili_gchen_5257@hotmail.com>
> Date: Wed, 5 Aug 2015 16:39:00 +0200

> On 8/5/15 12:32, Hans-Peter Nilsson wrote:
> >> From: Chen Gang <xili_gchen_5257@hotmail.com>
> >> Date: Mon, 20 Jul 2015 23:32:52 +0200
> > 
> >> On 7/9/15 08:44, Chen Gang wrote:
> >> The latest upstream cris gcc will cause issue for next-20150720 with
> >> allmodconfig (although it can let next-20150702 pass allmodconfig):
> >>
> >>     CC [M]  kernel/rcu/rcutorture.o
> > [...]
> >>   include/linux/rcutiny.h:55:20: internal compiler error: Segmentation fault
> >>    static inline void rcu_barrier_sched(void)
> >>                       ^
> >>   0xad879f crash_signal
> >>         ../../gcc/gcc/toplev.c:352
> >>   0xbf0fb8 tree_check(tree_node*, char const*, int, char const*, tree_code)
> >>         ../../gcc/gcc/tree.h:2857
> >>   0xbf0fb8 fold_builtin_alloca_with_align
> >>         ../../gcc/gcc/tree-ssa-ccp.c:2110
> > [...]
> > 
> >> If no any additional response, I shall try to fix it in the next month.
> > 
> > No need to enter a new bug report, this appears to be
> > <https://gcc.gnu.org/PR67055>.  It is also observed for other
> > ports, at least with the original C++ test-case there.  I added
> > a reduced rcutorture.c to the bug-report.  Thanks.
> > 
> 
> OK, thanks. :-)
> 
> And next, I shall try to cross compile kernel for another archs, hope I
> can start in 2015-08-15 -- during these days I am trying tilegx qemu for
> gcc testsuite (mainly for floating point insns and pending issues).

(Hopefully on-topic as the bug is likely to appear for multiple targets:)

Or pick up any gcc-6.0 snapshot later than or equal to r226616,
as a fix is now committed.  I just verified that the fix covers
the original and reduced kernel test-cases.  The fix is not on
the 5.x branch yet but I believe it is likely to be back-ported
in time for 5.3.

brgds, H-P

  reply	other threads:[~2015-08-05 16:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-04 22:30 Chen Gang
2015-07-07 12:05 ` Hans-Peter Nilsson
2015-07-09  0:44   ` Chen Gang
2015-07-20 21:32     ` Chen Gang
2015-08-05  4:32       ` Hans-Peter Nilsson
2015-08-05 14:39         ` Chen Gang
2015-08-05 16:56           ` Hans-Peter Nilsson [this message]
2015-08-04 14:45     ` Hans-Peter Nilsson

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=201508051656.t75GuRWq016534@ignucius.se.axis.com \
    --to=hans-peter.nilsson@axis.com \
    --cc=jespern@axis.com \
    --cc=linux-cris-kernel@axis.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=starvik@axis.com \
    --cc=xili_gchen_5257@hotmail.com \
    /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