From: Alexandre Oliva <oliva@adacore.com>
To: David Malcolm <dmalcolm@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH trunk] [PR104308] [analyzer] handle memmove like memcpy
Date: Thu, 08 Dec 2022 07:36:19 -0300 [thread overview]
Message-ID: <orfsdq41y4.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <20221202191104.3812885-1-dmalcolm@redhat.com> (David Malcolm's message of "Fri, 2 Dec 2022 14:11:04 -0500")
Hello again, David,
On Dec 2, 2022, David Malcolm <dmalcolm@redhat.com> wrote:
> I had a go at porting your patch to trunk; here's the result.
Oh, wow, nice! Thank you so much.
I confirm it works on riscv64-elf too.
--
Alexandre Oliva, happy hacker https://FSFLA.org/blogs/lxo/
Free Software Activist GNU Toolchain Engineer
Disinformation flourishes because many people care deeply about injustice
but very few check the facts. Ask me about <https://stallmansupport.org>
next prev parent reply other threads:[~2022-12-08 10:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 9:45 [PATCH gcc-12] " Alexandre Oliva
2022-12-02 19:11 ` [PATCH trunk] " David Malcolm
2022-12-08 10:36 ` Alexandre Oliva [this message]
2022-12-09 2:28 ` [committed] analyzer: " David Malcolm
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=orfsdq41y4.fsf@lxoliva.fsfla.org \
--to=oliva@adacore.com \
--cc=dmalcolm@redhat.com \
--cc=gcc-patches@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).