public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Marc Glisse <marc.glisse@inria.fr>
To: Toon Moene <toon@moene.org>
Cc: gcc mailing list <gcc@gcc.gnu.org>
Subject: Re: 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:44:07 +0100 (CET)	[thread overview]
Message-ID: <bdbe7eb6-2b1a-41da-831b-99b0259ec765@hippo.saclay.inria.fr> (raw)
In-Reply-To: <5e40b118-5868-e5e6-999c-9955433d5d02@moene.org>

On Tue, 1 Feb 2022, Toon Moene wrote:

> 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 ...

Maybe try with a more recent version of GMP first? gcd_1.c has only 103 
lines in release 6.2.1.

A stack trace (UBSAN_OPTIONS=print_stacktrace=1) would make it easier to 
guess where this is coming from.

-- 
Marc Glisse

  reply	other threads:[~2022-02-01 21:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-01 21:03 Toon Moene
2022-02-01 21:44 ` Marc Glisse [this message]
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=bdbe7eb6-2b1a-41da-831b-99b0259ec765@hippo.saclay.inria.fr \
    --to=marc.glisse@inria.fr \
    --cc=gcc@gcc.gnu.org \
    --cc=toon@moene.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).