public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/105879] DI mode constants are incorrectly loaded into registers on big-endian xtensa
Date: Wed, 08 Jun 2022 16:17:54 +0000	[thread overview]
Message-ID: <bug-105879-4-W5Zy80Reku@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105879-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-12 branch has been updated by Max Filippov
<jcmvbkbc@gcc.gnu.org>:

https://gcc.gnu.org/g:777a80af43eebb7506937cf04b54f17c4fce2b8e

commit r12-8466-g777a80af43eebb7506937cf04b54f17c4fce2b8e
Author: Max Filippov <jcmvbkbc@gmail.com>
Date:   Tue Jun 7 21:01:01 2022 -0700

    gcc: xtensa: fix PR target/105879

    split_double operates with the 'word that comes first in memory in the
    target' terminology, while gen_lowpart operates with the 'value
    representing some low-order bits of X' terminology. They are not
    equivalent and must be dealt with differently on little- and big-endian
    targets.

    gcc/
            PR target/105879
            * config/xtensa/xtensa.md (movdi): Rename 'first' and 'second'
            to 'lowpart' and 'highpart' so that they match 'gen_lowpart' and
            'gen_highpart' bitwise semantics and fix order of highpart and
            lowpart depending on target endianness.

    (cherry picked from commit e94c6dbfb57a862dd8a8685eabc4886ad1aaea25)

  parent reply	other threads:[~2022-06-08 16:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-08  4:07 [Bug target/105879] New: " jcmvbkbc at gcc dot gnu.org
2022-06-08  4:27 ` [Bug target/105879] " jcmvbkbc at gcc dot gnu.org
2022-06-08 15:48 ` cvs-commit at gcc dot gnu.org
2022-06-08 16:17 ` cvs-commit at gcc dot gnu.org [this message]
2022-06-08 16:25 ` cvs-commit at gcc dot gnu.org
2022-06-08 16:27 ` jcmvbkbc 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-105879-4-W5Zy80Reku@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).