public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/104307] [11/12 Regression] '-fcompare-debug' failure (length) w/ -mavx512f -O2
Date: Mon, 31 Jan 2022 14:38:55 +0000 [thread overview]
Message-ID: <bug-104307-4-ylSeraf1vs@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104307-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104307
--- Comment #1 from Arseny Solokha <asolokha at gmx dot com> ---
(In reply to Arseny Solokha from comment #0)
> w/ -Os -funroll-loops:
It's an obvious copy-paste error, of course. It fails the check w/ -mavx512f
-O2.
next prev parent reply other threads:[~2022-01-31 14:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 14:37 [Bug target/104307] New: " asolokha at gmx dot com
2022-01-31 14:38 ` asolokha at gmx dot com [this message]
2022-01-31 16:34 ` [Bug target/104307] " jakub at gcc dot gnu.org
2022-01-31 16:43 ` [Bug middle-end/104307] " jakub at gcc dot gnu.org
2022-01-31 16:53 ` jakub at gcc dot gnu.org
2022-02-01 15:06 ` [Bug tree-optimization/104307] " cvs-commit at gcc dot gnu.org
2022-02-01 15:10 ` [Bug tree-optimization/104307] [11 " jakub at gcc dot gnu.org
2022-02-19 8:02 ` cvs-commit at gcc dot gnu.org
2022-02-19 8:08 ` jakub 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-104307-4-ylSeraf1vs@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).