public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/110677] New: UBSAN error: load of value 1818451807, which is not a valid value for type 'expr_t' when compiling pr49213.f90
Date: Sat, 15 Jul 2023 19:54:27 +0000 [thread overview]
Message-ID: <bug-110677-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110677
Bug ID: 110677
Summary: UBSAN error: load of value 1818451807, which is not a
valid value for type 'expr_t' when compiling
pr49213.f90
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: jamborm at gcc dot gnu.org
Blocks: 63426
Target Milestone: ---
Host: x86_64-linux-gnu
Target: x86_64-linux-gnu
With master revision r14-2537-g18dac101678b8c and ubsan-bootstrapped compiler,
I am getting the following error when compiling our own test
gcc/testsuite/gfortran.dg/pr49213.f90:
worker@tiber:~/buildworker/tiber-gcc-ubsan/objdir/gcc>
UBSAN_OPTIONS="halt_on_error=1 print_stacktrace=1"
/home/worker/buildworker/tiber-gcc-ubsan/objdir/gcc/testsuite/gfortran3/../../gfortran
-B/home/worker/buildworker/tiber-gcc-ubsan/objdir/gcc/testsuite/gfortran3/../../
-B/home/worker/buildworker/tiber-gcc-ubsan/objdir/x86_64-pc-linux-gnu/./libgfortran/
/home/worker/buildworker/tiber-gcc-ubsan/build/gcc/testsuite/gfortran.dg/pr49213.f90
-fdiagnostics-plain-output -fdiagnostics-plain-output -O0 -pedantic-errors
-B/home/worker/buildworker/tiber-gcc-ubsan/objdir/x86_64-pc-linux-gnu/./libgfortran/.libs
-L/home/worker/buildworker/tiber-gcc-ubsan/objdir/x86_64-pc-linux-gnu/./libgfortran/.libs
-L/home/worker/buildworker/tiber-gcc-ubsan/objdir/x86_64-pc-linux-gnu/./libgfortran/.libs
-L/home/worker/buildworker/tiber-gcc-ubsan/objdir/x86_64-pc-linux-gnu/./libatomic/.libs
-B/home/worker/buildworker/tiber-gcc-ubsan/objdir/x86_64-pc-linux-gnu/./libquadmath/.libs
-L/home/worker/buildworker/tiber-gcc-ubsan/objdir/x86_64-pc-linux-gnu/./libquadmath/.libs
-L/home/worker/buildworker/tiber-gcc-ubsan/objdir/x86_64-pc-linux-gnu/./libquadmath/.libs
-lm -o /tmp/pr49213.exe
/home/worker/buildworker/tiber-gcc-ubsan/build/gcc/fortran/resolve.cc:1401:30:
runtime error: load of value 1818451807, which is not a valid value for type
'expr_t'
#0 0x79124e in resolve_structure_cons
/home/worker/buildworker/tiber-gcc-ubsan/build/gcc/fortran/resolve.cc:1401
#1 0xda4d76 in resolve_generic_f
/home/worker/buildworker/tiber-gcc-ubsan/build/gcc/fortran/resolve.cc:2852
#2 0xda4d76 in resolve_function
/home/worker/buildworker/tiber-gcc-ubsan/build/gcc/fortran/resolve.cc:3367
#3 0xda839e in gfc_resolve_expr(gfc_expr*)
/home/worker/buildworker/tiber-gcc-ubsan/build/gcc/fortran/resolve.cc:7313
#4 0xda839e in gfc_resolve_expr(gfc_expr*)
/home/worker/buildworker/tiber-gcc-ubsan/build/gcc/fortran/resolve.cc:7275
#5 0xdef0e0 in gfc_resolve_code(gfc_code*, gfc_namespace*)
/home/worker/buildworker/tiber-gcc-ubsan/build/gcc/fortran/resolve.cc:12314
#6 0xdfe227 in resolve_codes
/home/worker/buildworker/tiber-gcc-ubsan/build/gcc/fortran/resolve.cc:18027
#7 0xdfe09a in resolve_codes
/home/worker/buildworker/tiber-gcc-ubsan/build/gcc/fortran/resolve.cc:18008
#8 0xd8965a in gfc_resolve(gfc_namespace*)
/home/worker/buildworker/tiber-gcc-ubsan/build/gcc/fortran/resolve.cc:18062
#9 0xd8965a in gfc_resolve(gfc_namespace*)
/home/worker/buildworker/tiber-gcc-ubsan/build/gcc/fortran/resolve.cc:18041
#10 0xd3f387 in resolve_all_program_units
/home/worker/buildworker/tiber-gcc-ubsan/build/gcc/fortran/parse.cc:6862
#11 0xd3f387 in gfc_parse_file()
/home/worker/buildworker/tiber-gcc-ubsan/build/gcc/fortran/parse.cc:7118
#12 0xed0bfe in gfc_be_parse_file
/home/worker/buildworker/tiber-gcc-ubsan/build/gcc/fortran/f95-lang.cc:229
#13 0x2adde20 in compile_file
/home/worker/buildworker/tiber-gcc-ubsan/build/gcc/toplev.cc:444
#14 0xab5e55 in do_compile
/home/worker/buildworker/tiber-gcc-ubsan/build/gcc/toplev.cc:2126
#15 0xab5e55 in toplev::main(int, char**)
/home/worker/buildworker/tiber-gcc-ubsan/build/gcc/toplev.cc:2282
#16 0xab8fb1 in main
/home/worker/buildworker/tiber-gcc-ubsan/build/gcc/main.cc:39
#17 0x7fd8e6557baf in __libc_start_call_main (/lib64/libc.so.6+0x27baf)
(BuildId: 1390809fc3a065502adfa6735d294c2c86aebe4d)
#18 0x7fd8e6557c78 in __libc_start_main_alias_1 (/lib64/libc.so.6+0x27c78)
(BuildId: 1390809fc3a065502adfa6735d294c2c86aebe4d)
#19 0xab93f4 in _start ../sysdeps/x86_64/start.S:115
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63426
[Bug 63426] [meta-bug] Issues found with -fsanitize=undefined
next reply other threads:[~2023-07-15 19:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-15 19:54 jamborm at gcc dot gnu.org [this message]
2023-07-22 16:57 ` [Bug fortran/110677] " jamborm at gcc dot gnu.org
2023-08-14 17:41 ` jamborm at gcc dot gnu.org
2023-08-15 15:15 ` cvs-commit at gcc dot gnu.org
2023-08-15 15:19 ` jamborm 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-110677-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).