From: "Martin Jansa" <Martin.Jansa@gmail.com>
To: Martin Jansa <Martin.Jansa@gmail.com>
Cc: Khem Raj <raj.khem@gmail.com>, Ross Burton <ross@burtonini.com>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH v2] gcc: Update to latest on release/gcc-11 branch
Date: Wed, 26 May 2021 19:09:47 +0200 [thread overview]
Message-ID: <CA+chaQd8yVVJA=U1KieF_sPaQU-Yo0vcHAfkGnNLdTtE7uNw3g@mail.gmail.com> (raw)
In-Reply-To: <1682A83F9B9CCAC9.4904@lists.openembedded.org>
[-- Attachment #1: Type: text/plain, Size: 683 bytes --]
On Wed, May 26, 2021 at 5:43 PM Martin Jansa via lists.openembedded.org
<Martin.Jansa=gmail.com@lists.openembedded.org> wrote
> I'm seeing different error with gcc-sanitizers and this new revision:
>
> work-shared/gcc-11.1.0-r0/gcc-11.1.0/libsanitizer/lsan/lsan_common_linux.cpp:164:25:
> error: invalid conversion from 'void (*)(void*)' to 'void* (*)(void*)'
> [-fpermissive]
>
> will double-check if it was introduced by this upgrade or something else
> in oe-core master update today and also if there is a fix in even newer gcc
> already.
>
Sorry for noise, this line of code comes from our local patch and the
upgrade just started triggering this issue in it.
[-- Attachment #2: Type: text/html, Size: 1080 bytes --]
next prev parent reply other threads:[~2021-05-26 17:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 15:21 [PATCH v2] gcc: Update to latest on release/gcc-11 branch Khem Raj
2021-05-26 10:55 ` [OE-core] " Ross Burton
2021-05-26 14:18 ` Khem Raj
2021-05-26 15:43 ` Martin Jansa
[not found] ` <1682A83F9B9CCAC9.4904@lists.openembedded.org>
2021-05-26 17:09 ` Martin Jansa [this message]
[not found] ` <1682ACF8BD246772.22476@lists.openembedded.org>
2021-05-29 13:09 ` Martin Jansa
2021-05-29 17:16 ` 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='CA+chaQd8yVVJA=U1KieF_sPaQU-Yo0vcHAfkGnNLdTtE7uNw3g@mail.gmail.com' \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=ross@burtonini.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.