Linux SPARSE checker discussions
 help / color / mirror / Atom feed
From: "Jan Pokorný" <pokorny_jan@seznam.cz>
To: Christopher Li <sparse@chrisli.org>
Cc: linux-sparse@vger.kernel.org
Subject: Re: [PATCH] unify usage of VOID
Date: Mon, 11 Apr 2011 01:34:43 +0200	[thread overview]
Message-ID: <4DA23E93.8010105@seznam.cz> (raw)
In-Reply-To: <BANLkTi=VYG-YwbSXksBgUayZfwTOWtfYiQ@mail.gmail.com>

On 04/11/2011 12:20 AM, Christopher Li wrote:
> Hi Jan,
> 
> You are one fire with this sparse code :-)
> 
> I will take a closer look of your patch series tonight.
> 
> Thanks
> 
> Chris
> 
> 
> On Sun, Apr 10, 2011 at 9:24 AM, Jan Pokorný <pokorny_jan@seznam.cz> wrote:
>> Also remove unneeded empty initializator of `void_pseudo'.
>>
>> Signed-off-by: Jan Pokorny <pokorny_jan@seznam.cz>
>> ---
>>  linearize.c |    4 ++--
>>  1 files changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/linearize.c b/linearize.c
>> index f2034ce..46c9726 100644
>> --- a/linearize.c
>> +++ b/linearize.c
>> @@ -33,7 +33,7 @@ struct access_data;
>>  static pseudo_t add_load(struct entrypoint *ep, struct access_data *);
>>  static pseudo_t linearize_initializer(struct entrypoint *ep, struct expression *initializer, struct access_data *);
>>
>> -struct pseudo void_pseudo = {};
>> +struct pseudo void_pseudo;
>>
>>  static struct position current_pos;
>>
>> @@ -1880,7 +1880,7 @@ pseudo_t linearize_statement(struct entrypoint *ep, struct statement *stmt)
>>                struct basic_block *active;
>>                pseudo_t src = linearize_expression(ep, expr);
>>                active = ep->active;
>> -               if (active && src != &void_pseudo) {
>> +               if (active && src != VOID) {
>>                        struct instruction *phi_node = first_instruction(bb_return->insns);
>>                        pseudo_t phi;
>>                        if (!phi_node) {
>> --
>> 1.7.1
>> --

Hi Chris,

thank you for considering these patches, feel free to bother me with
complains :-)

I think I will have some more patches to send, but it should not be
tightly related to what I have already posted (if so, I'll make it explicit).

-- 
Jan
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2011-04-10 23:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-10 16:24 [PATCH] unify usage of VOID Jan Pokorný
2011-04-10 22:20 ` Christopher Li
2011-04-10 23:34   ` Jan Pokorný [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=4DA23E93.8010105@seznam.cz \
    --to=pokorny_jan@seznam.cz \
    --cc=linux-sparse@vger.kernel.org \
    --cc=sparse@chrisli.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