From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-rust@gcc.gnu.org
Subject: [Bug rust/108124] Rust: UBSAN issues when tests are run
Date: Thu, 15 Dec 2022 09:51:28 +0000 [thread overview]
Message-ID: <bug-108124-35322-s2Sjzl4iGt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108124-35322@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108124
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
./xgcc -B. /home/marxin/Programming/gcc/gcc/testsuite/rust/compile/macro19.rs
-w
/home/marxin/Programming/gcc/gcc/rust/ast/rust-stmt.h:342:48: runtime error:
load of value 190, which is not a valid value for type 'bool'
#0 0x3546c7e in Rust::AST::ExprStmtWithBlock::is_semicolon_followed() const
/home/marxin/Programming/gcc/gcc/rust/ast/rust-stmt.h:342
#1 0x3546c7e in
Rust::HIR::ASTLoweringStmt::visit(Rust::AST::ExprStmtWithBlock&)
/home/marxin/Programming/gcc/gcc/rust/hir/rust-ast-lower-stmt.h:78
#2 0x35510cd in Rust::HIR::ASTLoweringStmt::translate(Rust::AST::Stmt*,
bool*) /home/marxin/Programming/gcc/gcc/rust/hir/rust-ast-lower-stmt.h:42
#3 0x3521208 in Rust::HIR::ASTLoweringBlock::visit(Rust::AST::BlockExpr&)
/home/marxin/Programming/gcc/gcc/rust/hir/rust-ast-lower.cc:113
#4 0x354de9e in
Rust::HIR::ASTLoweringBlock::translate(Rust::AST::BlockExpr*, bool*)
/home/marxin/Programming/gcc/gcc/rust/hir/rust-ast-lower-block.h:36
#5 0x36ef7fa in Rust::HIR::ASTLoweringItem::visit(Rust::AST::Function&)
/home/marxin/Programming/gcc/gcc/rust/hir/rust-ast-lower-item.cc:428
#6 0x36b8646 in Rust::HIR::ASTLoweringItem::translate(Rust::AST::Item*)
/home/marxin/Programming/gcc/gcc/rust/hir/rust-ast-lower-item.cc:28
#7 0x351caeb in Rust::HIR::ASTLowering::go()
/home/marxin/Programming/gcc/gcc/rust/hir/rust-ast-lower.cc:75
#8 0x351f7d9 in Rust::HIR::ASTLowering::Resolve(Rust::AST::Crate&)
/home/marxin/Programming/gcc/gcc/rust/hir/rust-ast-lower.cc:65
#9 0x2afebf5 in Rust::Session::compile_crate(char const*)
/home/marxin/Programming/gcc/gcc/rust/rust-session-manager.cc:549
#10 0x2b0420e in Rust::Session::handle_input_files(int, char const**)
/home/marxin/Programming/gcc/gcc/rust/rust-session-manager.cc:362
#11 0x212ce46 in grs_langhook_parse_file
/home/marxin/Programming/gcc/gcc/rust/rust-lang.cc:184
#12 0xcf3b22e in compile_file
/home/marxin/Programming/gcc/gcc/toplev.cc:444
#13 0xcf4f14d in do_compile /home/marxin/Programming/gcc/gcc/toplev.cc:2125
#14 0xcf4f14d in toplev::main(int, char**)
/home/marxin/Programming/gcc/gcc/toplev.cc:2277
#15 0x10409e86 in main /home/marxin/Programming/gcc/gcc/main.cc:39
#16 0x7ffff6a2c5af in __libc_start_call_main (/lib64/libc.so.6+0x275af)
#17 0x7ffff6a2c678 in __libc_start_main_impl (/lib64/libc.so.6+0x27678)
#18 0x212cbd4 in _start ../sysdeps/x86_64/start.S:115
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-12-15 9:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 9:47 [Bug rust/108124] New: " marxin at gcc dot gnu.org
2022-12-15 9:47 ` [Bug rust/108124] Rust: " marxin at gcc dot gnu.org
2022-12-15 9:51 ` marxin at gcc dot gnu.org [this message]
2022-12-15 9:57 ` [Bug rust/108124] Rust: ASAN&UBSAN " marxin at gcc dot gnu.org
2023-04-26 6:57 ` rguenth at gcc dot gnu.org
2023-07-27 9:24 ` rguenth at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-108124-35322-s2Sjzl4iGt@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-rust@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).