From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Ramsay Jones <ramsay@ramsayjones.plus.com>
Cc: linux-sparse@vger.kernel.org
Subject: Re: [PATCH 2/3] add more testcases for AND/OR simplification
Date: Sun, 6 Sep 2020 23:15:34 +0200 [thread overview]
Message-ID: <20200906211534.wtbedsju2rdo22j6@ltop.local> (raw)
In-Reply-To: <a845a6af-39bc-c936-0e0c-401025960ac6@ramsayjones.plus.com>
On Sun, Sep 06, 2020 at 09:12:21PM +0100, Ramsay Jones wrote:
>
>
> On 06/09/2020 20:10, Luc Van Oostenryck wrote:
> > On Sun, Sep 06, 2020 at 05:38:54PM +0100, Ramsay Jones wrote:
> >> On 06/09/2020 13:40, Luc Van Oostenryck wrote:
>
> >> Hmm, I can't see an optimization for these two! :(
> >> Care to explain just what you expect? (maybe with an
> >> '*.expected' file?)
> >
> > I saw your other email about it but I just would like to add
> > these sort of tests should really be read at the IR level,
> > the output of 'test-linearize $file.c'. Sometimes, the C file
> > is just a convoluted way to create some specific sequence of
> > IR instructions. Also, often the name of the file and the
>
> Yeah, indeed - which is kinda why I would have liked to see
> an '*.expected' file! It is just hard to try looking at the
> C code and imagine the likely optimization opportunities and
> the effect they have on the IR. :-D
>
> Having said that, I do understand why you would rather not do
> that. It just makes reviewing such patches a hard job, requiring
Yes, sorry. I realized this only now.
I've added a very small comment with the expected result to
the tests.
-- Luc
next prev parent reply other threads:[~2020-09-06 21:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-06 12:40 [PATCH 0/3] fix & extend mask related testcases Luc Van Oostenryck
2020-09-06 12:40 ` [PATCH 1/3] add more testcases for existing AND/OR simplifications Luc Van Oostenryck
2020-09-06 16:12 ` Ramsay Jones
2020-09-06 18:52 ` Luc Van Oostenryck
2020-09-06 12:40 ` [PATCH 2/3] add more testcases for AND/OR simplification Luc Van Oostenryck
2020-09-06 16:38 ` Ramsay Jones
2020-09-06 16:46 ` Ramsay Jones
2020-09-06 19:10 ` Luc Van Oostenryck
2020-09-06 20:12 ` Ramsay Jones
2020-09-06 21:15 ` Luc Van Oostenryck [this message]
2020-09-06 12:40 ` [PATCH 3/3] optim: fix some testcases related to bitfield manipulation Luc Van Oostenryck
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=20200906211534.wtbedsju2rdo22j6@ltop.local \
--to=luc.vanoostenryck@gmail.com \
--cc=linux-sparse@vger.kernel.org \
--cc=ramsay@ramsayjones.plus.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 NNTP newsgroup(s).