public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/108190] g++.target/i386/*pr54700*.C testcases fail on x86_64-mingw
Date: Wed, 21 Dec 2022 10:55:36 +0000	[thread overview]
Message-ID: <bug-108190-4-QoN34W1IBv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108190-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Marc Glisse <glisse at gcc dot gnu.org> ---
Indeed, this looks like a common issue (at least with the x86 backend): the
memory load is combined with the comparison before we try combining the
comparison with the blend, and this last combination is then rejected because
it expects a register, not memory. So either we are too eager in merging loads
with instructions, or we reject instructions too early when we could still fix
the operands with an extra load.

      parent reply	other threads:[~2022-12-21 10:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-21  4:44 [Bug testsuite/108190] New: Various testsuite asm fails nightstrike at gmail dot com
2022-12-21  4:48 ` [Bug testsuite/108190] " nightstrike at gmail dot com
2022-12-21  4:49 ` [Bug testsuite/108190] g++.target/i386/*pr54700*.C testcases fail on x86_64-mingw pinskia at gcc dot gnu.org
2022-12-21  4:50 ` nightstrike at gmail dot com
2022-12-21  4:52 ` nightstrike at gmail dot com
2022-12-21  4:53 ` nightstrike at gmail dot com
2022-12-21 10:55 ` glisse 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-108190-4-QoN34W1IBv@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).