public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rsworktech at outlook dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/111448] New: g++ ICE Segmentation fault in qemu-riscv64-static emulator
Date: Mon, 18 Sep 2023 00:12:20 +0000	[thread overview]
Message-ID: <bug-111448-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 111448
           Summary: g++ ICE Segmentation fault in qemu-riscv64-static
                    emulator
           Product: gcc
           Version: 13.2.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: rsworktech at outlook dot com
  Target Milestone: ---

Created attachment 55918
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55918&action=edit
reduced ICE source file

Maybe this is technically not a gcc bug. But I very much appreciate any
suggestions and pointers you might give to me.

gcc doesn't fail on real riscv64 boards so looks more like a qemu bug to me. I
also reported it to qemu: https://gitlab.com/qemu-project/qemu/-/issues/1895

In a qemu-user Arch Linux riscv64
container(https://github.com/felixonmars/archriscv-packages/wiki/Setup-Arch-Linux-RISC-V-Development-Environment),
the attached source file(which has been reduced to less than 5kb by cvise)
caused an ICE, segmentation fault.

Command: g++ -S testcase.i -w -fpreprocessed -o /dev/null

Output: 

g++: internal compiler error: Segmentation fault signal terminated program
cc1plus
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
See <https://bugs.archlinux.org/> for instructions.

g++ -v
Using built-in specs.
COLLECT_GCC=g++
COLLECT_LTO_WRAPPER=/usr/lib/gcc/riscv64-unknown-linux-gnu/13.2.1/lto-wrapper
Target: riscv64-unknown-linux-gnu
Configured with: /build/gcc/src/gcc/configure
--enable-languages=c,c++,d,fortran,go,lto,objc,obj-c++ --enable-bootstrap
--prefix=/usr --libdir=/usr/lib --libexecdir=/usr/lib --mandir=/usr/share/man
--infodir=/usr/share/info --with-bugurl=https://bugs.archlinux.org/
--with-build-config=bootstrap-lto --with-linker-hash-style=gnu
--with-system-zlib --enable-__cxa_atexit --enable-cet=auto
--enable-checking=release --enable-clocale=gnu --enable-default-pie
--enable-default-ssp --enable-gnu-indirect-function --enable-gnu-unique-object
--enable-libstdcxx-backtrace --enable-link-serialization=1
--enable-linker-build-id --enable-lto --enable-plugin --enable-shared
--enable-threads=posix --disable-libssp --disable-libstdcxx-pch
--disable-multilib --disable-werror
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 13.2.1 20230801 (GCC)

             reply	other threads:[~2023-09-18  0:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-18  0:12 rsworktech at outlook dot com [this message]
2023-09-18  0:17 ` [Bug c++/111448] " pinskia at gcc dot gnu.org
2023-09-18  0:42 ` rsworktech at outlook dot com
2023-09-18  7:19 ` schwab@linux-m68k.org
2023-09-18 16:29 ` rsworktech at outlook dot com
2023-09-28  9:55 ` schwab@linux-m68k.org
2023-09-29  0:43 ` rsworktech at outlook dot com

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