From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] vlc: workaround microblaze gcc internal compiler error
Date: Mon, 27 Feb 2017 09:29:13 +0100 [thread overview]
Message-ID: <20170227092913.55b940f6@free-electrons.com> (raw)
In-Reply-To: <20170227060725.GA27933@waldemar-brodkorb.de>
Hello,
On Mon, 27 Feb 2017 07:07:25 +0100, Waldemar Brodkorb wrote:
> Override gcc optimization flags with -O0.
>
> The workaround is not required for gcc6 anymore, but
> gcc6 is disabled for microblaze, because it breaks startup
> of the system somehow. So the bug is not reported upstream.
If it's not required for gcc6, then perhaps we should add a
BR2_TOOLCHAIN_GCC_AT_LEAST_6 condition, so that this chunk gets a
chance to be removed at some point in the future.
> +# gcc bug internal compiler error: in merge_overlapping_regs, at regrename.c:304
> +ifeq ($(BR2_microblaze),y)
I.e.:
ifeq ($(BR2_microblaze):$(BR2_TOOLCHAIN_GCC_AT_LEAST_6),y:)
> +VLC_CONF_ENV += CFLAGS="$(TARGET_CFLAGS) -O0"
> +VLC_CONF_OPTS += --disable-optimizations
> +endif
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-02-27 8:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 6:07 [Buildroot] [PATCH] vlc: workaround microblaze gcc internal compiler error Waldemar Brodkorb
2017-02-27 8:29 ` Thomas Petazzoni [this message]
2017-02-27 20:38 ` 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=20170227092913.55b940f6@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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