public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aldyh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/106785] ICE in fail, at selftest.cc:47 since r13-2266-g8bb1df032cc080
Date: Wed, 31 Aug 2022 11:18:05 +0000	[thread overview]
Message-ID: <bug-106785-4-byr4NzUlKq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106785-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106785

--- Comment #1 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
(In reply to Martin Liška from comment #0)
> Fails for the following cross compilers:
> pdp11-aout  rx-elf  vax-linux-gnu  vax-netbsdelf
> 
> $ ./xgcc -v
> Using built-in specs.
> COLLECT_GCC=./xgcc
> Target: vax-linux-gnu
> Configured with: /home/marxin/Programming/gcc/configure
> --enable-languages=c,c++ --prefix=/home/marxin/bin/gcc --disable-multilib
> --disable-libsanitizer --disable-bootstrap --target=vax-linux-gnu :
> (reconfigured) /home/marxin/Programming/gcc/configure
> --enable-languages=c,c++ --prefix=/home/marxin/bin/gcc --disable-multilib
> --disable-libsanitizer --disable-bootstrap --target=vax-linux-gnu
> Thread model: posix
> Supported LTO compression algorithms: zlib zstd
> gcc version 13.0.0 20220830 (experimental) (GCC) 
> 
> $ make
> ./xgcc -B./ -B/home/marxin/bin/gcc/vax-linux-gnu/bin/ -isystem
> /home/marxin/bin/gcc/vax-linux-gnu/include -isystem
> /home/marxin/bin/gcc/vax-linux-gnu/sys-include -L/dev/shm/objdir2/gcc/../ld 
> -xc++ -nostdinc /dev/null -S -o /dev/null
> -fself-test=/home/marxin/Programming/gcc/gcc/testsuite/selftests
> /home/marxin/Programming/gcc/gcc/value-range.cc:3517: range_tests_nan: FAIL:
> ASSERT_NE (r0, r1)
> In function ‘test_fn’:
> cc1plus: internal compiler error: in fail, at selftest.cc:47
> 0x25b888b selftest::fail(selftest::location const&, char const*)
> 	/home/marxin/Programming/gcc/gcc/selftest.cc:47
> 0x1b554b8 range_tests_nan
> 	/home/marxin/Programming/gcc/gcc/value-range.cc:3517

Huh.  Does the VAX have different NAN rules, or is HONOR_NANS off by default on
it?

Either way, could you attach the .i file from the selftests if you still have
the build handy?

  reply	other threads:[~2022-08-31 11:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-31 11:01 [Bug rtl-optimization/106785] New: " marxin at gcc dot gnu.org
2022-08-31 11:18 ` aldyh at gcc dot gnu.org [this message]
2022-08-31 11:30 ` [Bug rtl-optimization/106785] " aldyh at gcc dot gnu.org
2022-08-31 11:33 ` aldyh at gcc dot gnu.org
2022-08-31 12:28 ` aldyh at gcc dot gnu.org
2022-08-31 12:41 ` jakub at gcc dot gnu.org
2022-08-31 13:12 ` aldyh at gcc dot gnu.org
2022-08-31 13:21 ` [Bug tree-optimization/106785] " aldyh at gcc dot gnu.org
2022-08-31 15:11 ` jakub at gcc dot gnu.org
2022-09-01  7:09 ` cvs-commit at gcc dot gnu.org
2022-09-01  7:12 ` aldyh 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-106785-4-byr4NzUlKq@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).