linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: [PATCH 2/5] unqual: unqualify_type() should check for null ctypes
Date: Wed, 18 Nov 2020 22:11:44 +0100	[thread overview]
Message-ID: <20201118211147.10680-3-luc.vanoostenryck@gmail.com> (raw)
In-Reply-To: <20201118211147.10680-1-luc.vanoostenryck@gmail.com>

It's possible that the input type is NULL, so add a check for it.

Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
---
 evaluate.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/evaluate.c b/evaluate.c
index c39f9ec73da9..fd84205c7f2c 100644
--- a/evaluate.c
+++ b/evaluate.c
@@ -63,6 +63,8 @@ static inline int valid_subexpr_type(struct expression *expr)
 
 static struct symbol *unqualify_type(struct symbol *ctype)
 {
+	if (!ctype)
+		return ctype;
 	if (ctype->type == SYM_NODE && (ctype->ctype.modifiers & MOD_QUALIFIER)) {
 		struct symbol *unqual = alloc_symbol(ctype->pos, 0);
 
-- 
2.29.2


  parent reply	other threads:[~2020-11-18 21:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-18 21:11 [PATCH 0/5] fix qualifier dropping Luc Van Oostenryck
2020-11-18 21:11 ` [PATCH 1/5] unqual: add testcases Luc Van Oostenryck
2020-11-18 21:11 ` Luc Van Oostenryck [this message]
2020-11-18 21:11 ` [PATCH 3/5] unqual: comma expressions should drop qualifiers Luc Van Oostenryck
2020-11-18 21:11 ` [PATCH 4/5] unqual: statement " Luc Van Oostenryck
2020-11-18 21:11 ` [PATCH 5/5] unqual: pre- & post-increment/decrement should *not* " 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=20201118211147.10680-3-luc.vanoostenryck@gmail.com \
    --to=luc.vanoostenryck@gmail.com \
    --cc=linux-sparse@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 NNTP newsgroup(s).