From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: "Khem Raj" <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] gcc: Upgrade to 12.2.0
Date: Tue, 23 Aug 2022 16:49:44 +0200 [thread overview]
Message-ID: <20220823164944.774719d2@booty> (raw)
In-Reply-To: <20220820163903.3462152-1-raj.khem@gmail.com>
Hi Khem,
On Sat, 20 Aug 2022 09:39:03 -0700
"Khem Raj" <raj.khem@gmail.com> wrote:
> GCC 12.2 is the first bug-fix release from the GCC 12 branch containing
> important fixes for regressions and serious bugs in GCC 12.1 with more
> than 71 bugs fixed since the previous release comprising of a number
> of libstdc++ and C++ and fortran fixes [1]
>
> Remove backported patch to fix libsanitizers with glibc 2.36, its
> already present in 12.2
>
> [1] https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=12.2
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
Building with this patch I had a ccache compile failure on musl builds:
error: 'time_t' has not been declared
error: no declaration matches 'std::string core::Statistics::format_human_readable(const Config&, time_t, uint8_t, bool) const'
https://autobuilder.yoctoproject.org/typhoon/#/builders/64/builds/5735/steps/11/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/45/builds/5752/steps/11/logs/stdio
They disappeared after removing this patch and rebuilding.
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2022-08-23 14:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-20 16:39 [PATCH] gcc: Upgrade to 12.2.0 Khem Raj
2022-08-23 14:49 ` Luca Ceresoli [this message]
2022-08-23 17:16 ` [OE-core] " Khem Raj
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=20220823164944.774719d2@booty \
--to=luca.ceresoli@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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.