From: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
To: Dan Carpenter <error27@gmail.com>
Cc: smatch@vger.kernel.org
Subject: Re: Build problem smatch 1.75
Date: Tue, 5 May 2026 20:28:53 +0530 [thread overview]
Message-ID: <9edbf5ef-a1bf-4e81-ad34-9766b06f9a3a@oracle.com> (raw)
In-Reply-To: <afnJPh_95KcWrnpx@stanley.mountain>
On 05/05/26 16:11, Dan Carpenter wrote:
>>> What compiler are you using? This is a bug in Sparse. We should
>>> probably fix it there.
>>>
> I reported this to the Sparse devs, but for now I just changed this to a
> memset() to fix the build in Smatch.
Thanks a lot Dan.
Regards,
Harshit
prev parent reply other threads:[~2026-05-05 14:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 7:55 Build problem smatch 1.75 Harshit Mogalapalli
2026-05-04 8:20 ` Dan Carpenter
2026-05-04 10:47 ` Harshit Mogalapalli
2026-05-05 10:41 ` Dan Carpenter
2026-05-05 14:58 ` Harshit Mogalapalli [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=9edbf5ef-a1bf-4e81-ad34-9766b06f9a3a@oracle.com \
--to=harshit.m.mogalapalli@oracle.com \
--cc=error27@gmail.com \
--cc=smatch@vger.kernel.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