From: Peter Korsgaard <peter@korsgaard.com>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: Romain Naour <romain.naour@gmail.com>,
Chris Packham <judge.packham@gmail.com>,
Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/2] package/syslog-ng: work around gcc bug 101915
Date: Wed, 14 Sep 2022 23:23:07 +0200 [thread overview]
Message-ID: <878rmlps5g.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20220806222203.1115664-2-giulio.benetti@benettiengineering.com> (Giulio Benetti's message of "Sun, 7 Aug 2022 00:22:02 +0200")
>>>>> "Giulio" == Giulio Benetti <giulio.benetti@benettiengineering.com> writes:
> With Microblaze Gcc version 12.1.0 the build fails due to gcc bug
> 101915: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101915. The bug
> show up when building syslog-ng with optimization but not when building
> with -O0. To work around this, if BR2_TOOLCHAIN_HAS_GCC_BUG_101915=y,
> we force using -O0.
> Fixes:
> http://autobuild.buildroot.net/results/b57/b57d51ed320a8e1bbfcf8d44875c113d868f82ee/
> Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
Committed to 2022.05.x and 2022.02.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-09-14 21:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-06 22:22 [Buildroot] [PATCH 1/2] toolchain/Config.in: update gcc bug 101915 comment Giulio Benetti
2022-08-06 22:22 ` [Buildroot] [PATCH 2/2] package/syslog-ng: work around gcc bug 101915 Giulio Benetti
2022-09-14 21:23 ` Peter Korsgaard [this message]
2022-08-07 12:58 ` [Buildroot] [PATCH 1/2] toolchain/Config.in: update gcc bug 101915 comment Thomas Petazzoni via buildroot
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=878rmlps5g.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=judge.packham@gmail.com \
--cc=romain.naour@gmail.com \
--cc=thomas.de_schampheleire@nokia.com \
--cc=thomas.petazzoni@bootlin.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 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.