From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14581] qemu-system-ppc -M mac99 does not boot for glibc system
Date: Mon, 14 Feb 2022 20:35:36 +0000 [thread overview]
Message-ID: <bug-14581-163-tUG7NhAbr8@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-14581-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=14581
--- Comment #1 from romain.naour@gmail.com ---
Hi Waldemar,
Thanks for the report!
I can reproduce it easily with gcc-10 and gcc-11 but not with gcc-9.
The powerpc 7400 support has been broken since the beginning of gcc-10
development.
After the commit [1] removing -many from the options passed by default to the
assembler, the build of this defconfig fail with assembler errors:
arch/powerpc/perf/bhrb.S: Assembler messages:
arch/powerpc/perf/bhrb.S:22: Error: unrecognized opcode: `cmpldi'
arch/powerpc/perf/bhrb.S:24: Error: unrecognized opcode: `ld'
arch/powerpc/perf/bhrb.S:25: Error: unrecognized opcode: `sldi'
It was fixed later by the commit [2] before the gcc-10 release but glibc
segfault at runtime since then.
The Buildroot gitlab-ci testing only test with uClibc-ng libc but I try
sometime with Glibc... but I missed this issue.
This issue should be reported to gcc.
[1]
https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=e154242724b084380e3221df7c08fcdbd8460674
[2]
https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=66711279083121b07d909ac0fc2f3a744ac7c937
Best regards,
Romain
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-02-14 20:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 13:46 [Buildroot] [Bug 14581] New: qemu-system-ppc -M mac99 does not boot for glibc system bugzilla
2022-02-14 20:35 ` bugzilla [this message]
2024-06-15 15:00 ` [Buildroot] [Bug 14581] " bugzilla
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-14581-163-tUG7NhAbr8@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.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