public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/106442] Build time error "vadd.i32 q3, q3, q0'" in case of -mcpu=cortex-m55+nofp+nomve.fp
Date: Tue, 26 Jul 2022 10:09:05 +0000	[thread overview]
Message-ID: <bug-106442-4-8VzNPAGZgi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106442-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106442

--- Comment #8 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
(In reply to sherry.zhang2 from comment #7)
> (In reply to Richard Earnshaw from comment #6)
> > possibly a dup of pr101723.  Please try gcc-11.3
> 
> The latest version I can get is 11.2
> https://developer.arm.com/tools-and-software/open-source-software/developer-
> tools/gnu-toolchain/downloads. Has GCC 11.3 been published?

https://gcc.gnu.org/pipermail/gcc-announce/2022/000170.html

      parent reply	other threads:[~2022-07-26 10:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-26  6:49 [Bug libgcc/106442] New: Build time error "vadd.i32 q3,q3,q0'" " sherry.zhang2 at arm dot com
2022-07-26  6:54 ` [Bug target/106442] Build time error "vadd.i32 q3, q3, q0'" " pinskia at gcc dot gnu.org
2022-07-26  6:56 ` pinskia at gcc dot gnu.org
2022-07-26  7:19 ` sherry.zhang2 at arm dot com
2022-07-26  7:25 ` pinskia at gcc dot gnu.org
2022-07-26  7:36 ` sherry.zhang2 at arm dot com
2022-07-26  9:47 ` rearnsha at gcc dot gnu.org
2022-07-26  9:54 ` sherry.zhang2 at arm dot com
2022-07-26 10:09 ` rearnsha at gcc dot gnu.org [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=bug-106442-4-8VzNPAGZgi@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).