Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1200396 > unrolled thread

Re: [Consult] cris: arch-v10: About $dtp0 register

Started byHans-Peter Nilsson <hans-peter.nilsson@axis.com>
First post2015-08-05 06:40 +0200
Last post2015-08-05 19:00 +0200
Articles 3 — 2 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [Consult] cris: arch-v10: About $dtp0 register Hans-Peter Nilsson <hans-peter.nilsson@axis.com> - 2015-08-05 06:40 +0200
    Re: [Consult] cris: arch-v10: About $dtp0 register Chen Gang <xili_gchen_5257@hotmail.com> - 2015-08-05 16:40 +0200
      Re: [Consult] cris: arch-v10: About $dtp0 register Hans-Peter Nilsson <hans-peter.nilsson@axis.com> - 2015-08-05 19:00 +0200

#1200396 — Re: [Consult] cris: arch-v10: About $dtp0 register

FromHans-Peter Nilsson <hans-peter.nilsson@axis.com>
Date2015-08-05 06:40 +0200
SubjectRe: [Consult] cris: arch-v10: About $dtp0 register
Message-ID<pTYEG-7oG-1@gated-at.bofh.it>
> 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.

brgds, H-P
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [next] | [standalone]


#1200829

FromChen Gang <xili_gchen_5257@hotmail.com>
Date2015-08-05 16:40 +0200
Message-ID<pU81k-483-17@gated-at.bofh.it>
In reply to#1200396
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).

Thanks.
-- 
Chen Gang

Open, share, and attitude like air, water, and life which God blessed
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]


#1200989

FromHans-Peter Nilsson <hans-peter.nilsson@axis.com>
Date2015-08-05 19:00 +0200
Message-ID<pUacO-7dQ-21@gated-at.bofh.it>
In reply to#1200829
> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web