Linux SPARSE checker discussions
 help / color / mirror / Atom feed
From: Ramsay Jones <ramsay@ramsayjones.plus.com>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: linux-sparse@vger.kernel.org
Subject: Re: [PATCH] no needs to use MARK_CURRENT_DELETED() for multi-jumps
Date: Sat, 17 Apr 2021 17:18:31 +0100	[thread overview]
Message-ID: <YHsKV2s9XW4w8tK9@satellite> (raw)
In-Reply-To: <20210417133154.53987-1-luc.vanoostenryck@gmail.com>

On Sat, Apr 17, 2021 at 03:31:54PM +0200, Luc Van Oostenryck wrote:
> MARK_CURRENT_DELETED() was added for the case(s) where an element
> must be removed from the list but the address of the other elements
> must not be changed. In this case of effectively removing the
> element from it list, the element is 'marked' as deleted in the list
> and the list walking macros will later take this in account.
> 
> However, this is not never needed for multi-jumps.

s/not never/not ever/ ?

ATB,
Ramsay Jones

> 
> So, use the usual DELETE_CURRENT_PTR() for them.
> 
> Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
> ---
>  simplify.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/simplify.c b/simplify.c
> index 9e3514d838a9..30d053f708e3 100644
> --- a/simplify.c
> +++ b/simplify.c
> @@ -2651,7 +2651,7 @@ static int simplify_cgoto(struct instruction *insn)
>  				continue;
>  			remove_bb_from_list(&jmp->target->parents, bb, 1);
>  			remove_bb_from_list(&bb->children, jmp->target, 1);
> -			MARK_CURRENT_DELETED(jmp);
> +			DELETE_CURRENT_PTR(jmp);
>  		} END_FOR_EACH_PTR(jmp);
>  		kill_use(&insn->src);
>  		insn->opcode = OP_BR;
> -- 
> 2.31.1
> 

  reply	other threads:[~2021-04-17 16:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-17 13:31 [PATCH] no needs to use MARK_CURRENT_DELETED() for multi-jumps Luc Van Oostenryck
2021-04-17 16:18 ` Ramsay Jones [this message]
2021-04-17 16:38   ` Luc Van Oostenryck
2021-04-17 17:46     ` Ramsay Jones

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=YHsKV2s9XW4w8tK9@satellite \
    --to=ramsay@ramsayjones.plus.com \
    --cc=linux-sparse@vger.kernel.org \
    --cc=luc.vanoostenryck@gmail.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