public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: felix <felixclc@protonmail.com>
To: "overseers@sourceware.org" <overseers@sourceware.org>
Subject: New account creation on sourceware for Glibc bug reporting and tracking
Date: Thu, 03 Feb 2022 14:58:16 +0000	[thread overview]
Message-ID: <Opa_kYWa_aIEUmETzAN0RA2lcb3KnJ7mv9Eem1KX7C63Xw5C06IAyHldn1gM0YR1rEmoNM6Y437lFuK3d1a6gnGHAhMxZJlqdNSQ-z6UJxM=@protonmail.com> (raw)

Hi there,

Was attempting to report a bug to upstream RE a performance regression I've been finding with certain structures related to GLIBC's implementation of malloc, but find myself being recommended to use the bugzilla and request an account to do so.

It's implementation seems to be causing issues with extra instructions being used and produced code being slower than alternative malloc implementations.

Thanks,

Felix C. LC.

             reply	other threads:[~2022-02-03 14:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-03 14:58 felix [this message]
2022-02-03 20:13 ` Mark Wielaard

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='Opa_kYWa_aIEUmETzAN0RA2lcb3KnJ7mv9Eem1KX7C63Xw5C06IAyHldn1gM0YR1rEmoNM6Y437lFuK3d1a6gnGHAhMxZJlqdNSQ-z6UJxM=@protonmail.com' \
    --to=felixclc@protonmail.com \
    --cc=overseers@sourceware.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).