From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] Xorg crash
Date: Thu, 05 May 2016 20:40:42 +0200 [thread overview]
Message-ID: <87vb2smjpx.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <572B84E6.1000503@zacarias.com.ar> (Gustavo Zacarias's message of "Thu, 5 May 2016 14:37:42 -0300")
>>>>> "Gustavo" == Gustavo Zacarias <gustavo@zacarias.com.ar> writes:
> On 05/05/16 14:31, Thomas Petazzoni wrote:
>> Hello,
>>
>> On Thu, 5 May 2016 11:33:13 -0300, Gustavo Zacarias wrote:
>>
>>> Try using BR2_OPTIMIZE_2=y and rebuild everything - the X server is
>>> notoriously fragile when optimizing for size with certain toolchain
>>> combinations/architectures.
>>
>> Should we:
>>
>> (1) Switch to -O2 as the default optimization level ?
>>
>> (2) Force -O2 for the X.org server ?
>>
>> Thomas
> Hi.
> From the little testing i've done it seems that switching the xorg
> server alone to -O2 is enough.
> I'm not a fan of "dark magic" scenarios, however it seems to be a
> recurring problem, at least for ARM & MIPS, doesn't seem to be the
> case for x86_64.
> I could make a couple test configs to see on which combinations it's
> failing by extending the Qemu ones, but it's probably more hassle than
> anything since there seems to be a wide spectrum of gcc versions
> affected.
> Going for -O2 might be the quickest solution, at least for xorg-server
> itself.
Yes, I agree. Simply forcing -O2 for xorg-server (with a sensible
comment explaining why) is good enough. People including Xorg are most
likely not as tight on space that -Os / -O2 matters much.
--
Venlig hilsen,
Peter Korsgaard
next prev parent reply other threads:[~2016-05-05 18:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-05 14:19 [Buildroot] Xorg crash Luca Ellero
2016-05-05 14:33 ` Gustavo Zacarias
2016-05-05 17:31 ` Thomas Petazzoni
2016-05-05 17:37 ` Gustavo Zacarias
2016-05-05 18:40 ` Peter Korsgaard [this message]
2016-05-06 6:20 ` Peter Seiderer
2016-05-06 6:54 ` Luca Ellero
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=87vb2smjpx.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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