From: "Martin Liška" <mliska@suse.cz>
To: Michael Eager <eager@eagerm.com>,
Waldemar Brodkorb <wbx@openadk.org>,
gcc@gcc.gnu.org
Cc: Ajit Agarwal <ajitkum@xilinx.com>,
buildroot@buildroot.org, dev@openadk.org,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Subject: Re: regression for microblaze architecture
Date: Wed, 09 Aug 2017 13:41:00 -0000 [thread overview]
Message-ID: <e48bbdf1-9fa7-a1e6-e88c-394ca26a6c57@suse.cz> (raw)
In-Reply-To: <5929A49C.1080803@eagerm.com>
On 05/27/2017 06:09 PM, Michael Eager wrote:
> On 05/27/2017 01:51 AM, Waldemar Brodkorb wrote:
>> Hi,
>>
>> Buildroot and OpenADK have samples to create a Linux system to be
>> bootup in Qemu system emulation for microblaze architecture.
>>
>> With gcc 6.3 and 7.1 the samples are not working anymore,
>> because the Linux system userland does not boot.
>> Qemu 2.9.0:
>> Kernel panic - not syncing: Attempted to kill init!
>> exitcode=0x0000000b
>> (with glibc, musl and uClibc-ng toolchains)
>>
>> I bisected gcc source code and found the bad commit:
>> 6dcad60c0ef48af584395a40feeb256fb82986a8
>>
>> When reverting the change, gcc 6.3 and 7.1 produces working
>> Linux rootfs again.
>>
>> What can we do about it?
>
> I will revert this commit in GCC.
>
>
Hi.
Looks the revert caused:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68485
Thanks,
Martin
prev parent reply other threads:[~2017-08-09 13:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-27 8:51 Waldemar Brodkorb
2017-05-27 14:44 ` [Buildroot] " Thomas Petazzoni
2017-05-27 16:09 ` Michael Eager
2017-05-27 18:30 ` Michael Eager
2017-08-09 13:41 ` Martin Liška [this message]
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=e48bbdf1-9fa7-a1e6-e88c-394ca26a6c57@suse.cz \
--to=mliska@suse.cz \
--cc=ajitkum@xilinx.com \
--cc=buildroot@buildroot.org \
--cc=dev@openadk.org \
--cc=eager@eagerm.com \
--cc=gcc@gcc.gnu.org \
--cc=thomas.petazzoni@free-electrons.com \
--cc=wbx@openadk.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).