public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/104063] New: gcc/fortran/trans-expr.c:5831:20: runtime error: load of value 215872256, which is not a valid value for type 'ar_type'
Date: Mon, 17 Jan 2022 10:53:18 +0000 [thread overview]
Message-ID: <bug-104063-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104063
Bug ID: 104063
Summary: gcc/fortran/trans-expr.c:5831:20: runtime error: load
of value 215872256, which is not a valid value for
type 'ar_type'
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
CC: burnus at gcc dot gnu.org, pault at gcc dot gnu.org
Blocks: 63426
Target Milestone: ---
I see the following UBSAN error:
$ ./xgcc -B.
/home/marxin/Programming/gcc/gcc/testsuite/gfortran.dg/pr103366.f90 -c
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-ubsan/build/gcc/fortran/trans-expr.c:5831:20:
runtime error: load of value 215872256, which is not a valid value for type
'ar_type'
#0 0x6bbab6 in gfc_conv_gfc_desc_to_cfi_desc
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-ubsan/build/gcc/fortran/trans-expr.c:5831
#1 0xf09be4 in gfc_conv_procedure_call(gfc_se*, gfc_symbol*,
gfc_actual_arglist*, gfc_expr*, vec<tree_node*, va_gc, vl_embed>*)
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-ubsan/build/gcc/fortran/trans-expr.c:6804
#2 0x1018cab in gfc_trans_call(gfc_code*, bool, tree_node*, tree_node*,
bool)
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-ubsan/build/gcc/fortran/trans-stmt.c:423
#3 0xe19807 in trans_code
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-ubsan/build/gcc/fortran/trans.c:1984
#4 0xedb754 in gfc_generate_function_code(gfc_namespace*)
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-ubsan/build/gcc/fortran/trans-decl.c:7651
#5 0xedb251 in gfc_generate_contained_functions
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-ubsan/build/gcc/fortran/trans-decl.c:5774
#6 0xedb251 in gfc_generate_function_code(gfc_namespace*)
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-ubsan/build/gcc/fortran/trans-decl.c:7583
#7 0xc597b4 in translate_all_program_units
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-ubsan/build/gcc/fortran/parse.c:6651
#8 0xc597b4 in gfc_parse_file()
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-ubsan/build/gcc/fortran/parse.c:6938
#9 0xdfc8ee in gfc_be_parse_file
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-ubsan/build/gcc/fortran/f95-lang.c:216
#10 0x2b34940 in compile_file
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-ubsan/build/gcc/toplev.c:452
#11 0x9cff59 in do_compile
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-ubsan/build/gcc/toplev.c:2158
#12 0x9cff59 in toplev::main(int, char**)
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-ubsan/build/gcc/toplev.c:2310
#13 0x9d5581 in main
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-ubsan/build/gcc/main.c:39
#14 0x7ffff78855bf in __libc_start_call_main
../sysdeps/nptl/libc_start_call_main.h:58
#15 0x7ffff788567b in __libc_start_main_impl ../csu/libc-start.c:409
#16 0x9d57a4 in _start
(/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-ubsan/objdir/gcc/f951+0x9d57a4)
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:[~2022-01-17 10:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 10:53 marxin at gcc dot gnu.org [this message]
2022-01-17 11:25 ` [Bug fortran/104063] " burnus 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-104063-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).