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/105981] [10/11/12/13 regression] Wrong code from gen_cpymem_ldrd_strd() with -mbig-endian
Date: Wed, 15 Jun 2022 13:40:47 +0000 [thread overview]
Message-ID: <bug-105981-4-izY8e61KSn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105981-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105981
Richard Earnshaw <rearnsha at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |10.5
Summary|Wrong code generated when |[10/11/12/13 regression]
|compiling for arm |Wrong code from
|cortex-a72 in AARCH32 with |gen_cpymem_ldrd_strd() with
|-mbig-endian |-mbig-endian
next prev parent reply other threads:[~2022-06-15 13:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 19:21 [Bug c/105981] New: Wrong code generated when compiling for arm cortex-a72 in AARCH32 " gjimenez at teldat dot com
2022-06-15 13:27 ` [Bug target/105981] " rearnsha at gcc dot gnu.org
2022-06-15 13:40 ` rearnsha at gcc dot gnu.org [this message]
2022-06-15 15:09 ` [Bug target/105981] [10/11/12/13 regression] Wrong code from gen_cpymem_ldrd_strd() " cvs-commit at gcc dot gnu.org
2022-06-15 15:10 ` [Bug target/105981] [10/11/12 " rearnsha at gcc dot gnu.org
2022-06-16 12:46 ` cvs-commit at gcc dot gnu.org
2022-06-16 12:46 ` cvs-commit at gcc dot gnu.org
2022-06-16 12:47 ` cvs-commit at gcc dot gnu.org
2022-06-16 12:51 ` rearnsha at gcc dot gnu.org
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-105981-4-izY8e61KSn@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).