public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Michael Eager <eager@eagerm.com>
To: 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: Sat, 27 May 2017 16:09:00 -0000	[thread overview]
Message-ID: <5929A49C.1080803@eagerm.com> (raw)
In-Reply-To: <20170527085122.GB24800@waldemar-brodkorb.de>

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.


-- 
Michael Eager	 eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306  650-325-8077

  parent reply	other threads:[~2017-05-27 16:09 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 [this message]
2017-05-27 18:30   ` Michael Eager
2017-08-09 13:41   ` Martin Liška

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=5929A49C.1080803@eagerm.com \
    --to=eager@eagerm.com \
    --cc=ajitkum@xilinx.com \
    --cc=buildroot@buildroot.org \
    --cc=dev@openadk.org \
    --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).