These are also easy to add and used in a unit test that I'd like to get working with the new interpreter.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
clang/lib/AST/Interp/ByteCodeExprGen.cpp | ||
---|---|---|
237 | Is there nothing special that has to happen when these are reference parameters? Can you at least add a test for that? |
clang/lib/AST/Interp/ByteCodeExprGen.cpp | ||
---|---|---|
237 | Umm, I don't really do references yet (I haven't tested them at all and I don't think they are implemented). |
clang/lib/AST/Interp/ByteCodeExprGen.cpp | ||
---|---|---|
237 | Hmm... that is unfortunate. We really should be doing references ASAP, as they are going to be a pretty critical/oft-needed during testing kinda thing. I'd at least want a commented-out test that you can re-enable ASAP. |
clang/lib/AST/Interp/ByteCodeExprGen.cpp | ||
---|---|---|
237 | Are not-yet-implemented features consistently implemented such that constant evaluation will fail with a (possibly unhelpful) diagnostic? As in https://godbolt.org/z/8vvdca9Ma? If so, can tests be added ahead of time with annotations for expected errors (essentially false positives to be addressed later)? |
clang/lib/AST/Interp/ByteCodeExprGen.cpp | ||
---|---|---|
237 | Some are always (like unhandled AST node), some are not. |
clang/lib/AST/Interp/ByteCodeExprGen.cpp | ||
---|---|---|
237 | An example for this with a reference type is in https://reviews.llvm.org/D132997 |
Is there nothing special that has to happen when these are reference parameters? Can you at least add a test for that?