From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/4] package/libtorrent-rasterbar: work around gcc bug 85180
Date: Sat, 22 Jun 2019 20:54:47 +0200 [thread overview]
Message-ID: <20190622205447.00350d77@windsurf> (raw)
In-Reply-To: <20190618084535.75870-5-giulio.benetti@micronovasrl.com>
On Tue, 18 Jun 2019 10:45:35 +0200
Giulio Benetti <giulio.benetti@micronovasrl.com> wrote:
> With Microblaze Gcc version < 8.x the build hangs due to gcc bug
> 85180: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85180. The bug
> shows up when building libtorrent-rasterbar with optimization but not
> when building with -O0. To work around this, if
> BR2_TOOLCHAIN_HAS_GCC_BUG_85180=y we force using -O0.
>
> Fixes:
> http://autobuild.buildroot.net/results/410/410e75676abc6bbabe9029ecda969e3d909f3e18/
>
> Signed-off-by: Giulio Benetti <giulio.benetti@micronovasrl.com>
> ---
> package/libtorrent-rasterbar/libtorrent-rasterbar.mk | 4 ++++
> 1 file changed, 4 insertions(+)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-06-22 18:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 8:45 [Buildroot] [PATCH 0/4] Microblaze clean up 2 Giulio Benetti
2019-06-18 8:45 ` [Buildroot] [PATCH 1/4] package/qt5/qt5base: disable predefined -Og optimization Giulio Benetti
2019-06-22 18:54 ` Thomas Petazzoni
2019-06-26 14:06 ` Giulio Benetti
2019-06-18 8:45 ` [Buildroot] [PATCH 2/4] toolchain: bug 90620 has not been fixed in gcc 8.x Giulio Benetti
2019-06-22 18:54 ` Thomas Petazzoni
2019-06-18 8:45 ` [Buildroot] [PATCH 3/4] package/qt5/qt5base: work around gcc bug 90620 Giulio Benetti
2019-06-22 18:54 ` Thomas Petazzoni
2019-06-18 8:45 ` [Buildroot] [PATCH 4/4] package/libtorrent-rasterbar: work around gcc bug 85180 Giulio Benetti
2019-06-22 18:54 ` Thomas Petazzoni [this message]
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=20190622205447.00350d77@windsurf \
--to=thomas.petazzoni@bootlin.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 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.