[llvm-branch-commits] [clang] [llvm] [Clang][Lex] Fix __has_include_next to return false when no valid next dir (PR #173717)

Yanzuo Liu via llvm-branch-commits llvm-branch-commits at lists.llvm.org
Sat Dec 27 04:39:39 PST 2025

Previous message: [llvm-branch-commits] [clang] [llvm] [Clang][Lex] Fix __has_include_next to return false when no valid next dir (PR #173717)
Next message: [llvm-branch-commits] [clang] [llvm] [Clang][Lex] Fix __has_include_next to return false when no valid next dir (PR #173717)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

zwuis wrote:

> bug not present in current git llvm22

Which commit fixed this bug?

https://github.com/llvm/llvm-project/pull/173717

Previous message: [llvm-branch-commits] [clang] [llvm] [Clang][Lex] Fix __has_include_next to return false when no valid next dir (PR #173717)
Next message: [llvm-branch-commits] [clang] [llvm] [Clang][Lex] Fix __has_include_next to return false when no valid next dir (PR #173717)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

More information about the llvm-branch-commits mailing list