public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/107090] [aarch64] sequence logic should be combined with mul and umulh
Date: Mon, 10 Oct 2022 04:30:09 +0000 [thread overview]
Message-ID: <bug-107090-4-wFik3x8yFP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107090-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107090
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Depends on| |103216
--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to vfdff from comment #5)
> Created attachment 53684 [details]
> Add A ? B + CST : B match and simplify optimizations
>
> Fix the 1st issue of the pattern match
There is a generic way of implementing this which I had posted at
https://gcc.gnu.org/pipermail/gcc-patches/2021-November/584411.html (you can
finish up that patch if you want).
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103216
[Bug 103216] missed optimization, phiopt/vrp?
next prev parent reply other threads:[~2022-10-10 4:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 17:51 [Bug c/107090] New: " zhongyunde at huawei dot com
2022-09-29 17:55 ` [Bug middle-end/107090] " pinskia at gcc dot gnu.org
2022-09-29 21:32 ` [Bug tree-optimization/107090] " pinskia at gcc dot gnu.org
2022-10-01 23:42 ` zhongyunde at huawei dot com
2022-10-01 23:51 ` pinskia at gcc dot gnu.org
2022-10-07 9:44 ` zhongyunde at huawei dot com
2022-10-10 4:22 ` zhongyunde at huawei dot com
2022-10-10 4:30 ` pinskia at gcc dot gnu.org [this message]
2022-10-10 9:49 ` zhongyunde at huawei dot com
2022-10-12 13:36 ` zhongyunde at huawei dot com
2022-10-12 21:33 ` pinskia at gcc dot gnu.org
2022-10-13 2:57 ` zhongyunde at huawei dot com
2022-10-29 1:54 ` zhongyunde at huawei dot com
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-107090-4-wFik3x8yFP@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).