From: bugzilla-daemon@kernel.org
To: linux-sparse@vger.kernel.org
Subject: [Bug 217153] New: [sparse-llvm] Support LLVM 15
Date: Tue, 07 Mar 2023 00:54:39 +0000 [thread overview]
Message-ID: <bug-217153-200559@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=217153
Bug ID: 217153
Summary: [sparse-llvm] Support LLVM 15
Product: Tools
Version: unspecified
Kernel Version: Any
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: enhancement
Priority: P1
Component: Sparse
Assignee: tools_sparse@kernel-bugs.kernel.org
Reporter: vladimir.petko@canonical.com
Regression: No
Created attachment 303890
--> https://bugzilla.kernel.org/attachment.cgi?id=303890&action=edit
remove LLVM 15 deprecated apis
Building sparse-llvm against LLVM 15 results in test failures due to the
segmentation faults
https://launchpadlibrarian.net/654787464/sparse_0.6.4-3_amd64-2023-03-06T19%3A31%3A07Z.build.
Would it be possible to consider a patch to migrate the sparse-llvm source code
to the opaque pointers at some point https://llvm.org/docs/OpaquePointers.html?
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
reply other threads:[~2023-03-07 0:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-217153-200559@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-sparse@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;
as well as URLs for NNTP newsgroup(s).