RIscRIpt added inline comments.
================
Comment at: clang/lib/Sema/SemaExpr.cpp:1972-1987
+ SmallString<64> Str;
+ llvm::raw_svector_ostream OS(Str);
+ Token Exp;
+ Exp.startToken();
+ if (Tok.getKind() == tok::kw_L__FUNCTION__ ||
+ Tok.getKind() == tok::kw_L__FUNCSIG__) {
+ OS << 'L';
----------------
cor3ntin wrote:
> RIscRIpt wrote:
> > cor3ntin wrote:
> > > I think it might be easier to create a string_literal token directly
> > > here. I'm also not sure we need to use `Lexer::Stringify`
> > > I think it might be easier to create a string_literal token directly here.
> >
> > What do you mean? Is there a function which creates Token object from
> > StringRef? Or is there a way to associate string literal value with a Token
> > without PP? I would like to simplify it, but I haven't found other ways of
> > achieving the same result.
> >
> > > I'm also not sure we need to use Lexer::Stringify
> >
> > Well, as far as I can see `StringLiteralParser` expands escape sequences.
> > So, I am just being too careful here.
> > If not using `Lexer::Stringify` do we want to assert that function name
> > does not contain neither `"` not `\` (which should not happen™)?
> Thanks! I really would get rid of `Stringify` here - I struggle to see how a
> function could be produced that has characters that cannot appear in an
> identifier. even asserting isn't very useful.
Replaced `Stringify` with enclosure into raw-string-literal. Despite
raw-string-literals are available starting from C++11, as far as I can see
`StringLiteralParser` does not check for the standard.
Let me know, if you believe we cannot abuse this fact, and we should keep using
`"regular string-literal"` for this purpose.
================
Comment at: clang/test/Sema/ms_predefined_expr.cpp:9
const char e[] = __PRETTY_FUNCTION__; // expected-warning{{initializing an
array from a '__PRETTY_FUNCTION__' predefined identifier is a Microsoft
extension}}
+ const wchar_t f[] = L__FUNCTION__; // expected-warning{{initializing an array
from a 'L__FUNCTION__' predefined identifier is a Microsoft extension}}
+ const wchar_t g[] = L__FUNCSIG__; // expected-warning{{initializing an array
from a 'L__FUNCSIG__' predefined identifier is a Microsoft extension}}
----------------
cor3ntin wrote:
> RIscRIpt wrote:
> > cor3ntin wrote:
> > > do we have any tests that look at the values of these things?
> > ```
> > clang/test/Analysis/eval-predefined-exprs.cpp
> > clang/test/AST/Interp/literals.cpp
> > clang/test/SemaCXX/source_location.cpp
> > clang/test/SemaCXX/predefined-expr.cpp
> > ```
> I think it's worth add a few more tests in
> clang/test/SemaCXX/predefined-expr.cpp checking concatenations
Added tests to check values of these string literals, as well as moved
`ms_wide_predefined_expr.cpp` tests into `ms_predefined_expr.cpp`.
Repository:
rG LLVM Github Monorepo
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D153914/new/
https://reviews.llvm.org/D153914
_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
