Open Quuxplusone opened 4 years ago
Bugzilla Link | PR44617 |
Status | NEW |
Importance | P normal |
Reported by | Dennis Felsing (dennis.felsing@sap.com) |
Reported on | 2020-01-22 01:41:41 -0800 |
Last modified on | 2020-01-23 01:48:00 -0800 |
Version | unspecified |
Hardware | PC Linux |
CC | alexfh@google.com, djasper@google.com, etienneb+llvm@google.com, eugene.zelenko@gmail.com, klimek@google.com, N.James93@hotmail.co.uk |
Fixed by commit(s) | |
Attachments | |
Blocks | |
Blocked by | |
See also |
I'm gonna guess the cause of this is the compiler can fold away the expression
to
>if constexpr(false || false) {}
Which is why the expression is redundant.
Would be interesting to see how it handles templated code where S is a typename.
In the same way. When we saw this in production it was actually with a template.
Then this bug only concerns template instantiations and in reality has nothing to do with it being in a constexpr if condition