From: Toon Moene <toon@moene.org>
To: gcc mailing list <gcc@gcc.gnu.org>
Subject: gcd_1.c:188:13: runtime error: shift exponent 64 is too large for 64-bit type 'long unsigned int'
Date: Tue, 1 Feb 2022 22:03:51 +0100 [thread overview]
Message-ID: <5e40b118-5868-e5e6-999c-9955433d5d02@moene.org> (raw)
I just ran a "ubsan" build on my x86_64-linux-gnu system.
See: https://gcc.gnu.org/pipermail/gcc-testresults/2022-February/754454.html
This is an interesting failure:
Executing on host:
/home/toon/scratch/bld1142336/gcc/testsuite/gfortran29/../../gfortran
-B/home/toon/scratch/bld1142336/gcc/testsuite/gfortran29/../../
-B/home/toon/scratch/bld1142336/x86_64-pc-linux-gnu/./libgfortran/
/home/toon/compilers/gcc/gcc/testsuite/gfortran.dg/graphite/pr39516.f
-fdiagnostics-plain-output -fdiagnostics-plain-output -O -O2
-ftree-loop-linear -S -o pr39516.s (timeout = 300)
spawn -ignore SIGHUP
/home/toon/scratch/bld1142336/gcc/testsuite/gfortran29/../../gfortran
-B/home/toon/scratch/bld1142336/gcc/testsuite/gfortran29/../../
-B/home/toon/scratch/bld1142336/x86_64-pc-linux-gnu/./libgfortran/
/home/toon/compilers/gcc/gcc/testsuite/gfortran.dg/graphite/pr39516.f
-fdiagnostics-plain-output -fdiagnostics-plain-output -O -O2
-ftree-loop-linear -S -o pr39516.s
gcd_1.c:188:13: runtime error: shift exponent 64 is too large for 64-bit
type 'long unsigned int'
FAIL: gfortran.dg/graphite/pr39516.f -O (test for excess errors)
Excess errors:
gcd_1.c:188:13: runtime error: shift exponent 64 is too large for 64-bit
type 'long unsigned int'
Note that the test case is pure Fortran source. The undefined error
seems to come from a function inside the graphite library ...
Kind regards,
--
Toon Moene - e-mail: toon@moene.org - phone: +31 346 214290
Saturnushof 14, 3738 XG Maartensdijk, The Netherlands
next reply other threads:[~2022-02-01 21:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 21:03 Toon Moene [this message]
2022-02-01 21:44 ` Marc Glisse
2022-02-02 8:57 ` Toon Moene
2022-02-02 9:11 ` Marc Glisse
2022-02-02 9:21 ` Toon Moene
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=5e40b118-5868-e5e6-999c-9955433d5d02@moene.org \
--to=toon@moene.org \
--cc=gcc@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).