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] [RISC-V] Segment fault if compiled with -static -pg
Date: Wed, 31 May 2023 22:35:41 +0000 [thread overview]
Message-ID: <bug-110066-4-QrhaUfwhZ2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110066-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110066
--- Comment #3 from rvalue <i at rvalue dot moe> ---
(In reply to Andrew Pinski from comment #1)
> This also could be a glibc issue.
I tried gcc 12.2.1 and 13.1.1 with exactly the same glibc and binutils
environments, the 12.2.1 version works while 13.1.1 doesn't. So I decide to
report it here.
Further analysis found that the identifier __EH_FRAME_BEGIN__ is different from
the address of .eh_frame section by 0x10, which is unexpected. I suspect the
linker might fail but that didn't change between the two runs.
next prev parent reply other threads:[~2023-05-31 22:35 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 20:36 [Bug target/110066] New: " i at rvalue dot moe
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 [this message]
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-QrhaUfwhZ2@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).