aboutsummaryrefslogtreecommitdiff
path: root/gcc/rust/backend/rust-compile-resolve-path.cc
diff options
context:
space:
mode:
authorbors[bot] <26634292+bors[bot]@users.noreply.github.com>2022-01-07 12:47:36 +0000
committerGitHub <noreply@github.com>2022-01-07 12:47:36 +0000
commit03e56b5181506a4e6cdb9fe86c543a57840e54c3 (patch)
tree9950e1acdb29638e42b5dc451e3232868ccfdf2c /gcc/rust/backend/rust-compile-resolve-path.cc
parent230b55bb532338fec1a9217f9ff8808cc0043772 (diff)
parent507dbac06d845af87e488dcb1f66390b4ca12de3 (diff)
downloadgcc-03e56b5181506a4e6cdb9fe86c543a57840e54c3.zip
gcc-03e56b5181506a4e6cdb9fe86c543a57840e54c3.tar.gz
gcc-03e56b5181506a4e6cdb9fe86c543a57840e54c3.tar.bz2
Merge #860
860: Add overflow checking on LiteralExpression r=philberty a=philberty This checks that the literal value is within the bounds of their respective types. I have omitted code fixing the other issue in the bug report that overflow/max_val integers should be saturated to infinity when cast to REAL_TYPE's this seems like something we really should have documentation to reference in the code as to why this is the correct Rust behaviour. Addresses #635 Co-authored-by: Philip Herron <philip.herron@embecosm.com>
Diffstat (limited to 'gcc/rust/backend/rust-compile-resolve-path.cc')
0 files changed, 0 insertions, 0 deletions