From: Thomas Huth <huth@tuxfamily.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/kmsxx: work around gcc bug 85180
Date: Fri, 7 Jun 2019 09:19:15 +0200 [thread overview]
Message-ID: <20190607091915.284a4c74@thl530.multi.box> (raw)
In-Reply-To: <7edbb3f8-65fa-4ea5-c2b4-e60b387ddac2@micronovasrl.com>
Am Fri, 7 Jun 2019 08:39:07 +0200
schrieb Giulio Benetti <giulio.benetti@micronovasrl.com>:
> Hello Thomas H.,
>
> adding Thomas P.+
>
> Il 07/06/2019 08:08, Thomas Huth ha scritto:
> > Am Thu, 6 Jun 2019 15:10:35 +0200
> > schrieb Giulio Benetti <giulio.benetti@micronovasrl.com>:
> >
> >> 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 kmsxx with optimization but not when
> >> building with -O0. To work around this, if
> >> BR2_TOOLCHAIN_HAS_GCC_BUG_85180=y we force using -O0.
> >
> > According to the description in the bugzilla, the bug should also go
> > away when compiling with -fno-dse ... so wouldn't it be better to
> > use "-fno-dse" here instead of disabling the optimizations
> > completely?
>
> Honestly I've completely missed that possible solution and didn't
> even tested.
>
> Anyway it's been discussed on IRC channel to keep a common work
> around for every different GCC_BUG_*, so since many packages are
> affected by Bug 85180 and -O0 seemed to work every time Thomas P.
> suggested to always keep that flag as solution.
Well, if -fno-dse is also "fixing" this bug, maybe you could add
"-fno-dse" to the global compiler flags instead of manually fixing each
and every package with -O0? ... anyway, just my 0.02 ?.
Thomas H
next prev parent reply other threads:[~2019-06-07 7:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 13:10 [Buildroot] [PATCH] package/kmsxx: work around gcc bug 85180 Giulio Benetti
2019-06-07 6:08 ` Thomas Huth
2019-06-07 6:39 ` Giulio Benetti
2019-06-07 7:19 ` Thomas Huth [this message]
2019-06-08 10:56 ` Arnout Vandecappelle
2019-06-08 11:51 ` Giulio Benetti
2019-06-08 12:46 ` Giulio Benetti
2019-06-08 13:00 ` Giulio Benetti
2019-06-13 16:43 ` Giulio Benetti
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=20190607091915.284a4c74@thl530.multi.box \
--to=huth@tuxfamily.org \
--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