From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: Romain Naour <romain.naour@gmail.com>,
Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 3/3] package/lmbench: fix build failure due to gcc bug 97208
Date: Sat, 14 Aug 2021 15:51:42 +0200 [thread overview]
Message-ID: <20210814155142.12c37943@windsurf> (raw)
In-Reply-To: <20210813213745.1555522-4-giulio.benetti@benettiengineering.com>
Hello Giulio,
On Fri, 13 Aug 2021 23:37:45 +0200
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:
> The lmbench package exhibits gcc bug 97208 when built for the Microblaze
> architecture with optimization enabled, which causes a build failure.
>
> As done for other packages in Buildroot work around this gcc bug by
> setting optimization to -O0 if BR2_TOOLCHAIN_HAS_GCC_BUG_97208=y..
>
> Fixes:
> http://autobuild.buildroot.net/results/ae1/ae1e4d61ed367c6cb64442c60d98882cc7985346/
>
> Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
Are we sure the gcc bug is the same? According to the word-around in
toolchain wrapper, disabling the -ftree-loop-distribute-patterns is
enough... but not for lmbench ?
What specifically tells us that the lmbench issue is the same as the
one we worked-around with -fnotree-loop-distribute-patterns in other
packages ?
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-08-14 13:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 21:37 [Buildroot] [PATCH 0/3] Microblaze gcc bug 97208 Giulio Benetti
2021-08-13 21:37 ` [Buildroot] [PATCH 1/3] toolchain: introduce BR2_TOOLCHAIN_HAS_GCC_BUG_97208 Giulio Benetti
2021-08-13 23:15 ` Giulio Benetti
2021-08-14 22:11 ` Giulio Benetti
2021-08-13 21:37 ` [Buildroot] [PATCH 2/3] toolchain/toolchain-wrapper: use Gcc bug 97208 instead of repeating it Giulio Benetti
2021-08-14 22:11 ` Giulio Benetti
2021-08-13 21:37 ` [Buildroot] [PATCH 3/3] package/lmbench: fix build failure due to gcc bug 97208 Giulio Benetti
2021-08-14 13:51 ` Thomas Petazzoni [this message]
2021-08-14 21:17 ` 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=20210814155142.12c37943@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=romain.naour@gmail.com \
--cc=thomas.de_schampheleire@nokia.com \
/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