public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "i at rvalue dot moe" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/110066] New: [RISC-V] Segment fault if compiled with -static -pg Date: Wed, 31 May 2023 20:36:07 +0000 [thread overview] Message-ID: <bug-110066-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110066 Bug ID: 110066 Summary: [RISC-V] Segment fault if compiled with -static -pg Product: gcc Version: 13.1.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: i at rvalue dot moe Target Milestone: --- When compile the code with option -static and -pg, the compiled program will fail with segfault before entering main(). Reproduce: $ gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/riscv64-unknown-linux-gnu/13.1.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.1.1 20230429 (GCC) $ cat > test.c int main(){} $ gcc test.c -o test -static -pg $ ./test Segmentation fault (core dumped) gdb backtrace: #0 classify_object_over_fdes () #1 __register_frame_info () #2 frame_dummy () #3 __libc_start_main_impl () #4 _start ()
next reply other threads:[~2023-05-31 20:36 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-31 20:36 i at rvalue dot moe [this message] 2023-05-31 20:39 ` [Bug target/110066] " pinskia at gcc dot gnu.org 2023-05-31 21:00 ` schwab@linux-m68k.org 2023-05-31 22:35 ` i at rvalue dot moe 2023-07-21 16:21 ` aurelien at aurel32 dot net 2023-07-22 5:16 ` pinskia at gcc dot gnu.org 2023-07-22 5:18 ` pinskia at gcc dot gnu.org 2023-07-22 8:46 ` aurelien at aurel32 dot net 2023-07-22 8:46 ` aurelien at aurel32 dot net 2023-07-22 8:47 ` aurelien at aurel32 dot net 2023-07-22 12:37 ` aurelien at aurel32 dot net 2023-07-22 14:50 ` aurelien at aurel32 dot net 2023-07-22 15:30 ` aurelien at aurel32 dot net 2023-07-22 15:53 ` [Bug target/110066] [13/14 Regression] " pinskia at gcc dot gnu.org 2023-07-22 15:56 ` pinskia at gcc dot gnu.org 2023-07-22 16:57 ` aurelien at aurel32 dot net 2023-07-22 17:02 ` pinskia at gcc dot gnu.org 2023-07-22 17:32 ` schwab@linux-m68k.org 2023-07-22 17:36 ` aurelien at aurel32 dot net 2023-07-22 17:36 ` schwab@linux-m68k.org 2023-07-22 20:32 ` pinskia at gcc dot gnu.org 2023-07-23 1:07 ` pinskia at gcc dot gnu.org 2023-07-23 4:55 ` cvs-commit at gcc dot gnu.org 2023-07-23 4:57 ` [Bug target/110066] [13 " pinskia at gcc dot gnu.org 2023-07-27 9:26 ` rguenth at gcc dot gnu.org 2023-08-04 11:15 ` aurelien at aurel32 dot net 2023-09-04 6:26 ` i at rvalue dot moe 2024-05-08 16:08 ` cvs-commit at gcc dot gnu.org 2024-05-08 16:08 ` pinskia 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-110066-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: linkBe 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).