mailing list of musl libc
 help / color / mirror / code / Atom feed
From: JeanHeyd Meneide <phdofthehouse@gmail.com>
To: musl@lists.openwall.com
Subject: [ Guidance ] Potential New Routines; Requesting Help
Date: Tue, 24 Dec 2019 18:06:50 -0500	[thread overview]
Message-ID: <CANHA4Oie9gY0munzvHDXdEq8486FvO4BCjM9s_QYpVQga2wNww@mail.gmail.com> (raw)

Dear musl Maintainers and Contributors,

     I hope this e-mail finds you doing well this Holiday Season! I am
interested in developing a few fast routines for text encoding for
musl after the positive reception of a paper for the C Standard
related to fast conversion routines:

     https://thephd.github.io/vendor/future_cxx/papers/source/C%20-%20Efficient%20Character%20Conversions.html

     While I have a basic implementation, I would like to use some
processor and compiler intrinsics to make it faster and make sure my
first contribution meets both quality and speed standards for a C
library.

     Is there a place in the codebase I can look to for guidance on
how to handle intrinsics properly within musl libc? If there is
already infrastructure and common idioms in place, I would rather use
that then starting to spin up my own.

Sincerely,
JeanHeyd Meneide


             reply	other threads:[~2019-12-24 23:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-24 23:06 JeanHeyd Meneide [this message]
2019-12-25 20:07 ` Florian Weimer
2019-12-26  2:13   ` Rich Felker
2019-12-26  5:43     ` JeanHeyd Meneide
2019-12-30 17:28       ` Rich Felker
2019-12-30 18:53         ` JeanHeyd Meneide
2019-12-26  9:43     ` Florian Weimer
2019-12-30 17:31 ` Rich Felker
2019-12-30 18:39   ` JeanHeyd Meneide
2019-12-30 19:57     ` Rich Felker
2019-12-31  3:58       ` JeanHeyd Meneide

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=CANHA4Oie9gY0munzvHDXdEq8486FvO4BCjM9s_QYpVQga2wNww@mail.gmail.com \
    --to=phdofthehouse@gmail.com \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).