Fixes PR39858
Details
- Reviewers
rsmith rjmccall efriedma - Commits
- rG9f935e874979: [ExprConstant] Handle compound assignment when LHS has integral type and RHS…
rL349444: [ExprConstant] Handle compound assignment when LHS has integral type and RHS…
rC349444: [ExprConstant] Handle compound assignment when LHS has integral type and RHS…
Diff Detail
- Repository
- rC Clang
Event Timeline
clang/lib/AST/ExprConstant.cpp | ||
---|---|---|
3427 ↗ | (On Diff #177708) | Parentheses ? It is always nicer to be able to read this |
clang/test/SemaCXX/constant-expression-cxx1y.cpp | ||
343 ↗ | (On Diff #177708) | Why remove a *= 3 instead of just adding a *= 3.1. |
345 ↗ | (On Diff #177708) | same |
clang/test/SemaCXX/constant-expression-cxx1y.cpp | ||
---|---|---|
343 ↗ | (On Diff #177708) | Because adding a *= 3.1 here will change the result of the whole calculation? |
Added parentheses. Restored the original tests and added more tests to the end of this function.
clang/lib/AST/ExprConstant.cpp | ||
---|---|---|
3441 ↗ | (On Diff #177719) | Can we more fundamentally restructure this entire handler so that, if the compound assignment's computation result type is an arithmetic type, we just promote both operands to that type, do the arithmetic there, and then coerce back down? This is C++, so the LHS type imposes almost no restrictions on the RHS type; also, this is Clang, where we support way too many arithmetic types for our own good. |
clang/lib/AST/ExprConstant.cpp | ||
---|---|---|
3441 ↗ | (On Diff #177719) | It seems the conditional statement is unavoidable, because APSInt and APFloat can't be handled at the same time (i.e. you need to choose among Handle{Int,Float}To{Int,Float}Cast, and between handleIntIntBinOp/handleFloatFloatBinOp). Maybe it's possible to add a layer that can accept both APSInt and APFloat, but it seems like an overkill if it's only used in the compound assignment case. |
clang/lib/AST/ExprConstant.cpp | ||
---|---|---|
3453 ↗ | (On Diff #177719) | Does this work for the float += int case? |
clang/lib/AST/ExprConstant.cpp | ||
---|---|---|
3441 ↗ | (On Diff #177719) | But we can have HandleValueTo{Int,Float}Cast functions that start with an arbitrary APValue and do the switch on that type, and we can have a HandleValueValueBinOp function that asserts that its operands have the same type and does the switch, and those two together should be good enough for what we need here. |
3453 ↗ | (On Diff #177719) | IIRC, the RHS gets promoted to the computation type in Sema. |
clang/lib/AST/ExprConstant.cpp | ||
---|---|---|
3441 ↗ | (On Diff #177719) | That's what I mean by "add a layer", and I think it's unworthy. Maybe it makes more sense as part of a larger scale rewrite, but that's more than I can deal with. |
clang/lib/AST/ExprConstant.cpp | ||
---|---|---|
3441 ↗ | (On Diff #177719) | Ah, I see that all three found methods here are called directly. I agree that this makes a rewrite that tries to handle the other cases here harder. Please at least adjust the code to make the || (!RHS.isInt() && !RHS.isFloat()) check redundant: put the int case in an if (RHS.isInt()) block (which should probably come before the isFloat() block) and emit a diagnostic if none of the cases are triggered. |
clang/lib/AST/ExprConstant.cpp | ||
---|---|---|
3453 ↗ | (On Diff #177719) | Yes, in the float += int case, the RHS is the result of ImplicitCastExpr of kind IntegralToFloating. And test_float() contains test for that case. |