From: Aldy Hernandez <aldyh@redhat.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: GCC patches <gcc-patches@gcc.gnu.org>,
Andrew MacLeod <amacleod@redhat.com>
Subject: Re: [PATCH] Add support for vrange streaming.
Date: Thu, 27 Apr 2023 13:36:54 +0200 [thread overview]
Message-ID: <CAGm3qMVV_6R7+9WUsO+2FR3Z96n0qwsEsDxhEgqjaKs+=G41Ug@mail.gmail.com> (raw)
In-Reply-To: <CAFiYyc3W8CoQ48mpf9y3nCOmP28yN+AbFx1VxVAt_s81nbq-YQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1021 bytes --]
Thanks. I will put it aside until I start posting the IPA patches.
Aldy
On Thu, Apr 27, 2023, 13:02 Richard Biener <richard.guenther@gmail.com>
wrote:
> On Tue, Apr 18, 2023 at 2:48 PM Aldy Hernandez <aldyh@redhat.com> wrote:
> >
> >
> >
> > On 4/18/23 11:06, Aldy Hernandez wrote:
> > > I think it's time for the ranger folk to start owning range streaming
> > > instead of passes (IPA, etc) doing their own thing. I have plans for
> > > overhauling the IPA code later this cycle to support generic ranges,
> > > and I'd like to start cleaning up the streaming and hashing interface.
> > >
> > > This patch adds generic streaming support for vrange.
> > >
> > > I'd appreciate another set of eyes.
> > >
> > > Thoughts?
> >
> > We recently added support for querying and storing an frange's NAN
> > without the need to be friends with the class.
> >
> > Adjusted patch in testing...
>
> I think this is reasonable once you find use for it.
>
> Thanks,
> Richard.
>
> > Aldy
>
>
next prev parent reply other threads:[~2023-04-27 11:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 9:06 Aldy Hernandez
2023-04-18 9:06 ` [PATCH] Add inchash support for vrange Aldy Hernandez
2023-04-18 9:17 ` Aldy Hernandez
2023-04-18 9:33 ` Jakub Jelinek
2023-04-18 10:32 ` Jakub Jelinek
2023-04-18 10:50 ` Aldy Hernandez
2023-04-18 10:59 ` Jakub Jelinek
2023-04-18 11:33 ` Aldy Hernandez
2023-04-18 11:34 ` Jakub Jelinek
2023-04-18 12:48 ` [PATCH] Add support for vrange streaming Aldy Hernandez
2023-04-27 11:00 ` Richard Biener
2023-04-27 11:36 ` Aldy Hernandez [this message]
2023-05-17 14:08 ` 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='CAGm3qMVV_6R7+9WUsO+2FR3Z96n0qwsEsDxhEgqjaKs+=G41Ug@mail.gmail.com' \
--to=aldyh@redhat.com \
--cc=amacleod@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
/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).