From: robert.jarzmik@free.fr (Robert Jarzmik)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM: pxa/corgi: armv5te kernel 4.12 fails to decompress compiled with gcc7
Date: Thu, 20 Jul 2017 08:57:14 +0200 [thread overview]
Message-ID: <87a83zsiid.fsf@belgarion.home> (raw)
In-Reply-To: <CAAQYJAvR2_wqf2Axe4aVMOu08t7w5tNEjK0s3fw_oemtqCRo7g@mail.gmail.com> (Andrea Adami's message of "Wed, 19 Jul 2017 15:13:29 +0200")
Andrea Adami <andrea.adami@gmail.com> writes:
> Hello,
Hi Andrea,
I have the same report on userspace side on buildroot from Petr [1], which
triggers endless segfaults in userspace (init) with gcc7 while everything is
fine with gcc6. I have confirmation on my test farm the problem happens as well.
Since debugging in userspace is far easier, I would suggest attacking the debug
with Petr on userspace side, and once sorted out, come back to kernel side.
Cheers.
--
Robert
[1] Mail from Petr
From: Petr Cvek <petrcvekcz@gmail.com>
Subject: cross-gcc
To: robert.jarzmik at free.fr
Date: Wed, 12 Jul 2017 02:37:35 +0200 (1 week, 1 day, 6 hours ago)
Message-ID: <ea45c82f-35a8-a908-d199-c72c0c801340@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
Hi,
do you still have a PXA27x board? I'm trying to build a rootfs with a new GCC
(7.1 from crosstool-ng snapshot a few days ago, buildroot same way) and it keeps
segfaulting (busybox, sshd, udevd, Xorg). Do you have the same problem? (seems
it does not care for xscale/iwmmxt neither O1/O2/Os, maybe on O0).
The GCC 6.x was fine and if i will need to make a bug report I think I will need
confirmation.
next prev parent reply other threads:[~2017-07-20 6:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 13:13 ARM: pxa/corgi: armv5te kernel 4.12 fails to decompress compiled with gcc7 Andrea Adami
2017-07-20 6:57 ` Robert Jarzmik [this message]
2017-09-02 21:50 ` Andrea Adami
2017-10-14 21:50 ` Aaro Koskinen
2017-10-14 21:57 ` Robert Jarzmik
2017-10-15 10:46 ` Aaro Koskinen
2017-10-15 13:01 ` Russell King - ARM Linux
2017-10-15 15:14 ` Aaro Koskinen
2017-10-16 11:55 ` Petr Cvek
2017-10-17 8:02 ` Andrea Adami
2017-10-17 8:10 ` Petr Cvek
2017-10-17 8:18 ` Andrea Adami
2017-10-18 10:39 ` Petr Cvek
2017-10-18 10:44 ` Russell King - ARM Linux
2017-10-18 11:12 ` Petr Cvek
2017-10-24 8:34 ` Andrea Adami
2017-10-24 8:43 ` Andrea Adami
2017-10-17 20:33 ` Aaro Koskinen
2017-10-18 9:57 ` Petr Cvek
2017-10-14 22:00 ` Petr Cvek
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=87a83zsiid.fsf@belgarion.home \
--to=robert.jarzmik@free.fr \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.