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/49959] ABS pattern is not recognized Date: Sun, 07 May 2023 04:49:05 +0000 [thread overview] Message-ID: <bug-49959-4-Gae9DtlOx9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49959-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49959 --- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Created attachment 55016 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55016&action=edit Patch For some reason it didn't make it to the mailing list yet. Will figure out why in a few. patches 2 and 3 did make it though.
next prev parent reply other threads:[~2023-05-07 4:49 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-08-03 12:25 [Bug middle-end/49959] New: " enkovich.gnu at gmail dot com 2011-08-03 12:50 ` [Bug tree-optimization/49959] " rguenth at gcc dot gnu.org 2012-01-21 8:21 ` pinskia at gcc dot gnu.org 2021-07-06 8:21 ` pinskia at gcc dot gnu.org 2021-11-17 10:11 ` pinskia at gcc dot gnu.org 2023-05-07 4:49 ` pinskia at gcc dot gnu.org [this message] 2023-05-08 7:38 ` cvs-commit at gcc dot gnu.org 2023-05-08 7:41 ` pinskia 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-49959-4-Gae9DtlOx9@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: linkBe 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).