tbaeder added inline comments.
================ Comment at: clang/lib/AST/Interp/ByteCodeExprGen.cpp:683-685 + // C++17 onwards require that we evaluate the RHS first. + // Compute RHS and save it in a temporary variable so we can + // load it again later. ---------------- aaron.ballman wrote: > In C, the evaluation of the operands are unsequenced. C doesn't currently > have constexpr functions, only constexpr objects, but that eliminates > mutating operations like compound assignment... for the moment. Perhaps a > FIXME comment for figuring out how to handle C? > > (The situation I'm worried about in C is with UB dealing with unsequenced > operations, like rejecting: https://godbolt.org/z/W11jchrKc) Could C make them sequenced when introducing constexpr functions? :) Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D149550/new/ https://reviews.llvm.org/D149550 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
