=?utf-8?b?8J+NjFNoYXdu?= <[email protected]>, =?utf-8?b?8J+NjFNoYXdu?= <[email protected]>, =?utf-8?b?8J+NjFNoYXdu?= <[email protected]>, =?utf-8?b?8J+NjFNoYXdu?= <[email protected]> Message-ID: In-Reply-To: <llvm.org/llvm/llvm-project/pull/[email protected]>
yronglin wrote: Hmm, I'm confuse about this fix. If there has a reproduce can tigger the null pointer dereference, before this patch, clang will crash, but after this patch, clang also will hit an assertion failure. So I don't think this is fix doesn't make sense. We need a reproducer which can tigger the crash issue with latest clang. Could you explain the root cause or provide a simple reproducer that can tigger clang crash? https://github.com/llvm/llvm-project/pull/192051 _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
