public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "romain.naour at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/98784] New: [gcc 8.4/9.3/10] sparcv8 regression
Date: Thu, 21 Jan 2021 22:13:09 +0000 [thread overview]
Message-ID: <bug-98784-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98784
Bug ID: 98784
Summary: [gcc 8.4/9.3/10] sparcv8 regression
Product: gcc
Version: 10.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: romain.naour at gmail dot com
Target Milestone: ---
Hello,
When building a rootfs for sparcv8 using the Buildroot defconfig
qemu_sparc_ss10_defconfig, the system produce some illegal instruction
messages.
gcc 8.3, 9.2 are the latest working gcc version.
git bisect between gcc 8.3 and 8.4 allowed to identify the commit that
introduced the regression:
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=0a83f1a441d7aaadecb368c237b6ee70bd7b91d6
The commit has been introduced to fix the following bub:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92095
It has been backported to gcc 8.4 and 9.3.
Reverting this patch allowed to produce a working rootfs.
This issue can be reproduced using the following steps:
$ git://git.busybox.net/buildroot
$ cd buildroot/
$ git checkout 2020.11.1
$ make qemu_sparc_ss10_defconfig
$ make
$ ./output/images/start-qemu.sh
The kernel boot correctly but the login program (busybox) crash while trying to
login:
[...]
Starting syslogd:
Welcome to Buildroot
buildroot login: root
Welcome to Buildroot
buildroot login: root
For now, It's just a basic test that allow to reproduce the issue.
We can use a shell instead of init program but even with a simple command such
'ls' the system crash:
sh-5.0# ls
CPU: 0 PID: 1 Comm: sh Not tainted 4.19.16 #1
[f0022fbc :
do_exit+0x948/0x968 ]
[f000afec :
do_signal+0x5f8/0x79c ]
[f000b4b4 :
do_notify_resume+0x48/0x58 ]
[f0008c88 :
signal_p+0x14/0x24 ]
[0004b874 :
0x4b874 ]
Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004
Best regards,
Romain
next reply other threads:[~2021-01-21 22:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 22:13 romain.naour at gmail dot com [this message]
2021-01-21 23:01 ` [Bug c/98784] " ebotcazou at gcc dot gnu.org
2021-01-21 23:26 ` romain.naour at gmail dot com
2021-01-21 23:43 ` ebotcazou at gcc dot gnu.org
2021-01-22 7:33 ` [Bug target/98784] [8/9/10/11 Regression] " rguenth at gcc dot gnu.org
2021-01-23 11:43 ` romain.naour at gmail dot com
2021-01-23 17:33 ` ebotcazou at gcc dot gnu.org
2021-01-23 20:07 ` romain.naour at gmail dot com
2021-01-23 21:56 ` [Bug target/98784] [8/9/10/11 Regression] problematic build of uClibc with -fPIC ebotcazou at gcc dot gnu.org
2021-01-24 9:17 ` ebotcazou at gcc dot gnu.org
2021-01-26 21:24 ` romain.naour at gmail dot com
2021-01-26 22:29 ` romain.naour at gmail dot com
2021-04-09 8:08 ` rguenth at gcc dot gnu.org
2021-05-14 9:54 ` [Bug target/98784] [9/10/11/12 " jakub at gcc dot gnu.org
2021-06-01 8:19 ` rguenth at gcc dot gnu.org
2021-06-28 16:40 ` yann at sionneau dot net
2021-06-28 16:50 ` yann at sionneau dot net
2022-05-27 9:44 ` [Bug target/98784] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:43 ` jakub at gcc dot gnu.org
2023-07-07 10:38 ` [Bug target/98784] [11/12/13/14 " rguenth at gcc dot gnu.org
2023-08-08 9:51 ` wbx at openadk dot org
2024-04-30 15:05 ` [Bug target/98784] [11/12/13/14/15 " dm.chestnykh at gmail dot com
2024-04-30 17:55 ` dm.chestnykh at gmail dot com
2024-04-30 17:59 ` pinskia at gcc dot gnu.org
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=bug-98784-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).