public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/79173] add-with-carry and subtract-with-borrow support (x86_64 and others)
Date: Thu, 15 Jun 2023 07:07:17 +0000 [thread overview]
Message-ID: <bug-79173-4-NUhKET69Gy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-79173-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79173
--- Comment #18 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:b6ca11407d4f5d16ccfb580ea2d3d9aa08d7cd11
commit r14-1835-gb6ca11407d4f5d16ccfb580ea2d3d9aa08d7cd11
Author: Jakub Jelinek <jakub@redhat.com>
Date: Thu Jun 15 09:05:01 2023 +0200
i386: Add peephole2 patterns to improve add with carry or subtract with
borrow with memory destination [PR79173]
This patch adds various peephole2s which help to recognize add with
carry or subtract with borrow with memory destination.
2023-06-14 Jakub Jelinek <jakub@redhat.com>
PR middle-end/79173
* config/i386/i386.md (*sub<mode>_3, @add<mode>3_carry,
addcarry<mode>, @sub<mode>3_carry, *add<mode>3_cc_overflow_1): Add
define_peephole2 TARGET_READ_MODIFY_WRITE/-Os patterns to prefer
using memory destination in these patterns.
next prev parent reply other threads:[~2023-06-15 7:07 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-79173-4@http.gcc.gnu.org/bugzilla/>
2020-11-15 21:21 ` [Bug target/79173] " already5chosen at yahoo dot com
2020-11-15 21:24 ` already5chosen at yahoo dot com
2020-11-15 21:32 ` jakub at gcc dot gnu.org
2020-11-15 22:30 ` already5chosen at yahoo dot com
2020-11-15 22:45 ` already5chosen at yahoo dot com
2021-05-28 15:34 ` tkoenig at gcc dot gnu.org
2021-09-09 6:48 ` [Bug middle-end/79173] " pinskia at gcc dot gnu.org
2021-09-09 8:54 ` vincent-gcc at vinc17 dot net
2021-09-09 9:05 ` pinskia at gcc dot gnu.org
2023-06-05 7:17 ` jakub at gcc dot gnu.org
2023-06-05 13:01 ` chfast at gmail dot com
2023-06-06 12:01 ` jakub at gcc dot gnu.org
2023-06-06 16:12 ` jakub at gcc dot gnu.org
2023-06-15 7:07 ` cvs-commit at gcc dot gnu.org [this message]
2023-06-15 7:10 ` cvs-commit at gcc dot gnu.org
2023-06-15 7:16 ` cvs-commit at gcc dot gnu.org
2023-06-15 7:49 ` jakub at gcc dot gnu.org
2023-06-16 17:49 ` cvs-commit at gcc dot gnu.org
2023-06-17 15:37 ` law at gcc dot gnu.org
2023-06-17 16:34 ` jakub at gcc dot gnu.org
2023-06-20 18:18 ` cvs-commit at gcc dot gnu.org
2023-06-24 9:42 ` glisse at gcc dot gnu.org
2023-06-24 9:51 ` jakub at gcc dot gnu.org
2023-06-24 12:09 ` vincent-gcc at vinc17 dot net
2023-06-24 12:32 ` jakub at gcc dot gnu.org
2023-06-24 13:10 ` vincent-gcc at vinc17 dot net
2023-06-24 13:14 ` jakub at gcc dot gnu.org
2023-06-25 0:22 ` vincent-gcc at vinc17 dot net
2023-08-29 8:47 ` cvs-commit 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-79173-4-NUhKET69Gy@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).