poky.lists.yoctoproject.org archive mirror
 help / color / mirror / Atom feed
From: "Steve" <star@gmx.li>
To: poky@lists.yoctoproject.org
Subject: Re: [poky] gcc 11.3 bug (gcc bugzilla 101723) on armv7
Date: Mon, 21 Nov 2022 16:30:03 +0100	[thread overview]
Message-ID: <3709403d-9030-7100-2899-fca493ae5857@gmx.li> (raw)
In-Reply-To: <17295986615369AA.25787@lists.yoctoproject.org>

Am 20.11.22 um 17:59 schrieb Steve:
> Am 18.11.22 um 20:53 schrieb Khem Raj:
>> On Thu, Nov 17, 2022 at 10:27 PM Steve <star@gmx.li> wrote:
>>>
>>> Hi,
>>>
>>> I found that GCC 11.3 that is part of latest kirkstone 4.0.5 has a
>>> problem building tensorflow-lite. (git.yoctoproject.org/meta-tensorflow)
>>>
>>> Problem is similar as described here:
>>> https://github.com/google/XNNPACK/issues/2003
>>>
>>> There are options set to compile ( -march=armv8.2-a+dotprod
>>> -mfpu=neon-fp-armv8) that doesn't match to the processor (armv7)
>>>
>>> Following this issue
>>> and points to  patch in
>>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101723
>>>
>>> Which is related to gcc 9. But couldn't it be that it is not fixed in
>>> 11.3 too?
>>
>> Its in gcc11 as well see
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101723#c5
>>
>>>
>>> How is able to fix it or probably better ask: what can I do to get it
>>> working? Honestly, I don't understand much of it.
>>
>> are you seeing it on yocto master ?
>
> Good point. I need some time to check that. But even if it works, it is
> not a real solution. I need to build a defined state.
> The fix is not a new one. Wondering why it's not in (or I am wrong and
> it is just similar).
>
> Best regards,
> Steve

sorry, can't test Master right now, it is  another gcc (12.2 instead of
11.3) - but I need to be in 11.3. Please, if possible ad that patch to
kirkstone release.


      parent reply	other threads:[~2022-11-21 15:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAOuPNLh1+LhxH8yuQprUntwjibAP_iuwF7tXnHjfhAZhLCCG-A@mail.gmail.com>
     [not found] ` <CAOuPNLgEs7Obni8kOqgznv_mLW8JQ4cF0CUS8jaV6AXEhw6aOg@mail.gmail.com>
2022-11-14 16:46   ` [linux-yocto] Removing DISTRO_FEATURES from a specific machine type Richard Purdie
2022-11-14 16:47   ` Jose Quaresma
2022-11-16 16:39     ` [poky] Replace a (not working) download by adding a local file as mirror? Steve
2022-11-16 17:08       ` Richard Purdie
2022-11-16 17:17         ` Steve
     [not found]         ` <17282032224EB050.28573@lists.yoctoproject.org>
2022-11-18  6:27           ` [poky] gcc 11.3 bug (gcc bugzilla 101723) on armv7 Steve
2022-11-18 19:53             ` Khem Raj
2022-11-20 16:59               ` Steve
     [not found]               ` <17295986615369AA.25787@lists.yoctoproject.org>
2022-11-21 15:30                 ` Steve [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=3709403d-9030-7100-2899-fca493ae5857@gmx.li \
    --to=star@gmx.li \
    --cc=poky@lists.yoctoproject.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).