From: Peter Korsgaard <peter@korsgaard.com>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: Romain Naour <romain.naour@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] toolchain: fix gcc bug 99140 condition
Date: Sun, 27 Feb 2022 21:33:27 +0100 [thread overview]
Message-ID: <87o82s123s.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20220206142403.1644118-1-giulio.benetti@benettiengineering.com> (Giulio Benetti's message of "Sun, 6 Feb 2022 15:24:03 +0100")
>>>>> "Giulio" == Giulio Benetti <giulio.benetti@benettiengineering.com> writes:
> Gcc bug 99140 exhibits with gcc versions:
> - up to 7.x
> - 9.x
> - 10.x
> and doesn't show up with gcc versions:
> - 8.x
> - 11.x
> then moving BR2_TOOLCHAIN_GCC_AT_LEAST_9 to BR2_TOOLCHAIN_GCC_AT_LEAST_10
> makes gcc version 9 set as working but it's not. So let's back substitute
> BR2_TOOLCHAIN_GCC_AT_LEAST_10 with BR2_TOOLCHAIN_GCC_AT_LEAST_9.
> Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
Committed to 2021.11.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-02-27 20:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-06 9:08 [Buildroot] [PATCH] toolchain: update gcc bug 99410 Giulio Benetti
2022-02-06 10:58 ` Thomas Petazzoni via buildroot
2022-02-06 11:14 ` Arnout Vandecappelle
2022-02-06 11:33 ` Giulio Benetti
2022-02-06 11:34 ` Giulio Benetti
2022-02-06 14:24 ` [Buildroot] [PATCH] toolchain: fix gcc bug 99140 condition Giulio Benetti
2022-02-14 20:41 ` Arnout Vandecappelle
2022-02-27 20:33 ` Peter Korsgaard [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=87o82s123s.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox