All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] xserver_xorg-server: use -O2 build optimization level
Date: Fri, 6 May 2016 09:15:10 -0300	[thread overview]
Message-ID: <572C8ACE.4010307@zacarias.com.ar> (raw)
In-Reply-To: <20160506084734.56e5caad@gmx.net>

On 06/05/16 03:47, Peter Seiderer wrote:

> Thanks for the patch, will surely improve the 'out of the box' usability of buildroot,
> but I would prefer a 'blacklist' of known failing combinations and simply disable
> xserver (with comment why) in this case(s), the only know to me is RPi1:
>
>    BR2_ARCH="arm"
>    BR2_GCC_TARGET_CPU="arm1176jzf-s"
>    BR2_OPTIMIZE_S=y
>
> The perfect solution would be a fix for gcc (and/or xserver)...
>
> Regards,
> Peter

Hi Peter.
Isn't that a bit harsh?
I'm not 100% comfortable with this solution either, however blacklisting 
xorg will be messy to put it lightly.
Also finding the failing combinations will not be simple - it seems ARM 
in general is affected on several toolchain combinations, as is MIPS as 
well (both tested in Qemu) - so it goes beyond some particular platforms.
Another alternative could be finding the exact gcc option that's causing 
it diffing the output of --help=optimizers and trying enabling/disabling 
one by one until it's fixed or fails since this would probably help 
pinpoint the precise optimizations that's causing it (which would in 
turn help in making a minimal test case to help upstream).
Regards.

  parent reply	other threads:[~2016-05-06 12:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-06  0:08 [Buildroot] [PATCH] xserver_xorg-server: use -O2 build optimization level Gustavo Zacarias
2016-05-06  6:47 ` Peter Seiderer
2016-05-06  6:55   ` Peter Seiderer
2016-05-06 12:15   ` Gustavo Zacarias [this message]
2016-05-06 21:33     ` Peter Seiderer
2016-05-06 13:51 ` Thomas Petazzoni

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=572C8ACE.4010307@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --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 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.