diff options
| author | Mark Wielaard <mark@klomp.org> | 2021-08-14 23:38:11 +0200 |
|---|---|---|
| committer | Mark Wielaard <mark@klomp.org> | 2021-08-16 23:30:49 +0200 |
| commit | 5b229ddbf41c9e74fcce930c26101c1d34a5c9d1 (patch) | |
| tree | 43d75121ca9c9b69b3baf9ca04271d39b73e3b0b /gcc/rust/backend/rust-compile-resolve-path.cc | |
| parent | 52c1cdc9c63baeb090680daf6762c02362f2c6cd (diff) | |
| download | gcc-5b229ddbf41c9e74fcce930c26101c1d34a5c9d1.zip gcc-5b229ddbf41c9e74fcce930c26101c1d34a5c9d1.tar.gz gcc-5b229ddbf41c9e74fcce930c26101c1d34a5c9d1.tar.bz2 | |
Use builtin bool instead of creating new bool types for ComparisonExpr
The TypeCheckExpr creates a new TyTy::BoolType for a
ComparisonExpr. This new BoolType is unknown to TyTyResolveCompile
which causes a crash when trying to compile the inferred new
BoolType. Resolve this by looking up the builtin bool type.
The new "bools_eq.rs" testcase uses several bools which show
this issue.
Also the lhs and rhs types need to be compatible, but don't
need to be bool type themselves. So don't append the reference
to the inferred type. The existing "ifunaryexpr.rs" testcase
will fail without this fix.
Diffstat (limited to 'gcc/rust/backend/rust-compile-resolve-path.cc')
0 files changed, 0 insertions, 0 deletions