public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/61747] min,max pattern not always properly optimized (for sse4 targets)
Date: Fri, 21 Jul 2023 06:21:17 +0000 [thread overview]
Message-ID: <bug-61747-4-iqaJYraERO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61747-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61747
--- Comment #11 from rguenther at suse dot de <rguenther at suse dot de> ---
On Fri, 21 Jul 2023, pinskia at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61747
>
> --- Comment #10 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
> (In reply to CVS Commits from comment #8)
> > * g++.target/i386/pr61747.C: New testcase.
>
> The testcase fails now, I don't know what caused it to fail though:
> FAIL: g++.target/i386/pr61747.C -std=gnu++14 scan-assembler-times max 4
I failed to update it before pushing, it will be fixed with the next
push I do (currently re-testing)
prev parent reply other threads:[~2023-07-21 6:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-08 13:34 [Bug tree-optimization/61747] New: " vincenzo.innocente at cern dot ch
2014-07-08 14:57 ` [Bug tree-optimization/61747] " glisse at gcc dot gnu.org
2014-07-08 15:21 ` vincenzo.innocente at cern dot ch
2014-07-08 15:27 ` glisse at gcc dot gnu.org
2014-07-08 15:35 ` vincenzo.innocente at cern dot ch
2014-07-08 15:46 ` rguenth at gcc dot gnu.org
2021-12-13 0:13 ` pinskia at gcc dot gnu.org
2023-07-18 11:15 ` rguenth at gcc dot gnu.org
2023-07-20 7:51 ` cvs-commit at gcc dot gnu.org
2023-07-20 7:52 ` rguenth at gcc dot gnu.org
2023-07-21 5:37 ` pinskia at gcc dot gnu.org
2023-07-21 6:21 ` rguenther at suse dot de [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-61747-4-iqaJYraERO@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).