From: Jeff Johnston <jjohnstn@redhat.com>
To: Sebastian Huber <sebastian.huber@embedded-brains.de>
Cc: Newlib <newlib@sourceware.org>, devel <devel@rtems.org>
Subject: Re: [PATCH v2 0/4] Optimize red-black tree insert/extract
Date: Wed, 6 Oct 2021 14:10:51 -0400 [thread overview]
Message-ID: <CAOox84vo6VbO6HQDET4RHt1GA+6Z1NaG4KMaXO9jXc_q_fdfTA@mail.gmail.com> (raw)
In-Reply-To: <20211005153344.91266-1-sebastian.huber@embedded-brains.de>
Hi Sebastian,
LGTM. If no one else objects, I will merge tomorrow.
-- Jeff J.
On Tue, Oct 5, 2021 at 11:34 AM Sebastian Huber <
sebastian.huber@embedded-brains.de> wrote:
> Code coverage analysis of the red-black tree insert/extract operations
> defined
> in <sys/tree.h> showed that the macros contain dead code. This patch set
> simplifies some expressions and add specialized rotations.
>
> v2:
>
> Add comments in patch 3 and 4.
>
> Sebastian Huber (4):
> sys/tree.h: Simplify loop condition
> sys/tree.h: Simplify chain of conditions
> sys/tree.h: Add parent rotations
> sys/tree.h: Red child with black sibling rotations
>
> newlib/libc/include/sys/tree.h | 90 +++++++++++++++++++++++++++++++---
> 1 file changed, 82 insertions(+), 8 deletions(-)
>
> --
> 2.26.2
>
>
next prev parent reply other threads:[~2021-10-06 18:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 15:33 Sebastian Huber
2021-10-05 15:33 ` [PATCH v2] Align *utime*() with POSIX/glibc Sebastian Huber
2021-10-05 15:35 ` Sebastian Huber
2021-10-05 15:33 ` [PATCH v2 1/4] sys/tree.h: Simplify loop condition Sebastian Huber
2021-10-05 15:33 ` [PATCH v2 2/4] sys/tree.h: Simplify chain of conditions Sebastian Huber
2021-10-05 15:33 ` [PATCH v2 3/4] sys/tree.h: Add parent rotations Sebastian Huber
2021-10-05 15:33 ` [PATCH v2 4/4] sys/tree.h: Red child with black sibling rotations Sebastian Huber
2021-10-06 18:10 ` Jeff Johnston [this message]
2021-10-07 12:10 ` [PATCH v2 0/4] Optimize red-black tree insert/extract Sebastian Huber
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=CAOox84vo6VbO6HQDET4RHt1GA+6Z1NaG4KMaXO9jXc_q_fdfTA@mail.gmail.com \
--to=jjohnstn@redhat.com \
--cc=devel@rtems.org \
--cc=newlib@sourceware.org \
--cc=sebastian.huber@embedded-brains.de \
/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).