From: David Edelsohn <dje.gcc@gmail.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>, Aldy Hernandez <aldyh@redhat.com>
Subject: Re: [PATCH 00/23] prange: pointer ranges
Date: Thu, 9 May 2024 10:58:01 -0400 [thread overview]
Message-ID: <CAGWvnyk5tCzCFbXunBWyGk4B5C1Hhy-x8=B2z2xLWgka2dVQqA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 219 bytes --]
> Tested and benchmarked on x86-64 Linux.
Why aren't these patches being tested on all major architectures,
especially those available in the Compile Farm? At least for correctness,
if not performance.
Thanks, David
next reply other threads:[~2024-05-09 14:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 14:58 David Edelsohn [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-04 8:30 Aldy Hernandez
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='CAGWvnyk5tCzCFbXunBWyGk4B5C1Hhy-x8=B2z2xLWgka2dVQqA@mail.gmail.com' \
--to=dje.gcc@gmail.com \
--cc=aldyh@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).