public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joern Rennecke <joern.rennecke@embecosm.com>
To: Oleg Endo <oleg.endo@t-online.de>
Cc: Andrew Pinski <pinskia@gmail.com>, GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: RFA: crc builtin functions & optimizations
Date: Tue, 15 Mar 2022 13:00:33 +0000	[thread overview]
Message-ID: <CAMqJFCr5=zMkATJPC0MFbV=6UqooRmjDncagaYXHpWDa_hP1Og@mail.gmail.com> (raw)
In-Reply-To: <585c1ed8179b8de0765454a46cc0b2eea26b37d0.camel@t-online.de>

On Tue, 15 Mar 2022 at 02:17, Oleg Endo <oleg.endo@t-online.de> wrote:
> > In my own CRC library I've got ~30 'commonly used' CRC types, based on
> the following generic definition:
> > This being a library makes it relatively easy to tune and customize for
> various systems.

...

> How would that work together with your proposal?

With optabs, you can put in whatever you like into the
machine-specific expansion.

Or if we could put your library-using code into a default expansion that is used
if there's no optab expansion for the modes given, then the target can override
this for machine-specific methods using the optabs, and otherwise use
your library
method in the default expansion.

  reply	other threads:[~2022-03-15 13:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-15  0:32 Joern Rennecke
2022-03-15  1:04 ` Andrew Pinski
2022-03-15  2:17   ` Oleg Endo
2022-03-15 13:00     ` Joern Rennecke [this message]
     [not found]   ` <CAMqJFCoHyuNzRkfmWSM6VkeWVhPw8tv5UAhnNfPYcUMzS5jFiQ@mail.gmail.com>
2022-03-15 12:52     ` Fwd: " Joern Rennecke
2022-03-15 12:03 ` Martin Jambor
2022-03-15 14:45 ` Richard Biener
2022-03-15 15:15   ` Joern Rennecke
2022-03-16  8:15     ` Richard Biener
2022-03-16 17:02       ` Joern Rennecke
2022-03-16 20:23         ` Joern Rennecke
2022-03-15 19:54   ` Joern Rennecke

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='CAMqJFCr5=zMkATJPC0MFbV=6UqooRmjDncagaYXHpWDa_hP1Og@mail.gmail.com' \
    --to=joern.rennecke@embecosm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=oleg.endo@t-online.de \
    --cc=pinskia@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).