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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <201508050432.t754Wstb005185@ignucius.se.axis.com>
Date:	Wed, 5 Aug 2015 06:32:54 +0200
From:	Hans-Peter Nilsson <hans-peter.nilsson@...s.com>
To:	xili_gchen_5257@...mail.com
CC:	jespern@...s.com, starvik@...s.com, linux-kernel@...r.kernel.org,
	linux-cris-kernel@...s.com
Subject: Re: [Consult] cris: arch-v10: About $dtp0 register

> From: Chen Gang <xili_gchen_5257@...mail.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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/