public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Noah Goldstein <goldstein.w.n@gmail.com>
To: Girish Joshi <girish946@gmail.com>
Cc: Girish Joshi via Libc-alpha <libc-alpha@sourceware.org>,
	Siddhesh Poyarekar <siddhesh@gotplt.org>
Subject: Re: [PATCH] build: All microbenchmarks should output in JSON. (bug 27740)
Date: Sun, 5 Mar 2023 12:18:05 -0600	[thread overview]
Message-ID: <CAFUsyf+7C+9NAv0Z0-EqASyTq75Txt_742PFRmG_vdVD79tuHA@mail.gmail.com> (raw)
In-Reply-To: <CALkY8p_ukdAcmNTOeDNK+Vm3V7hK_S8pCkmeTcVz0BcpQXpdZg@mail.gmail.com>

On Sun, Mar 5, 2023 at 12:15 AM Girish Joshi via Libc-alpha
<libc-alpha@sourceware.org> wrote:
>
> Ping.
>
> Girish Joshi
>
>
> On Sun, Feb 19, 2023 at 6:20 PM Girish Joshi <girish946@gmail.com> wrote:
> >
> > Hello,
> > According to bug #27740 [1], I found that the following files need to
> > be updated.
> >
> >     - benchtests/bench-memccpy.c
> >     - benchtests/bench-strcasestr.c
> >     - benchtests/bench-strcpy_chk.c
> >     - benchtests/bench-strsep.c
> >     - benchtests/bench-strtok.c
> >
> > Also, the output json needs to be fixed in two files.
> >     - bench-math-inlines.c
> >     - bench-strcoll.c
> >
> > This patch fixes both of these things.
> > The output is tested using
> > benchtests/scripts/compare_strings.py.
> >
> > Please let me know if some correction is needed in this patch.

When applying:
```
Applying: build: All microbenchmarks should output in JSON. (bug 27740)
.git/rebase-apply/patch:235: trailing whitespace.
    json_element_string(&json_ctx, impl->name);
warning: 1 line adds whitespace errors.
```

Also can you please post the patch as inline text in the email? It
allows patchwork
to detect it and easier to inline comments during review.

Some general feedback:
1) The changes to `benchtests/bench-math-inlines.c`/`benchtests/bench-strcoll.c`
seem unrelated, can you make that a seperate patch.
2) You are missing some test parameters in most of the files (mostly `max_char`)
also `dlen` in `bench_strcpy_chk.c`. Can you make sure you get all of them that
are relevant to the input.

> >
> > Thanks,
> > Girish Joshi
> > girishjoshi.io
> >
> > [1]: https://sourceware.org/bugzilla/show_bug.cgi?id=27740

      reply	other threads:[~2023-03-05 18:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-19 12:50 Girish Joshi
2023-03-05  6:15 ` Girish Joshi
2023-03-05 18:18   ` Noah Goldstein [this message]

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=CAFUsyf+7C+9NAv0Z0-EqASyTq75Txt_742PFRmG_vdVD79tuHA@mail.gmail.com \
    --to=goldstein.w.n@gmail.com \
    --cc=girish946@gmail.com \
    --cc=libc-alpha@sourceware.org \
    --cc=siddhesh@gotplt.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).