public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bugdal at aerifal dot cx" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/97431] [SH] Python crashes with 'Segmentation fault with -finline-small-functions Date: Thu, 15 Oct 2020 00:36:30 +0000 [thread overview] Message-ID: <bug-97431-4-T4UmgfaChr@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97431-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97431 --- Comment #1 from Rich Felker <bugdal at aerifal dot cx> --- Do you have a complete disassembly of the function it crashed in and register dump at the point of crash? That would help.
next prev parent reply other threads:[~2020-10-15 0:36 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-15 0:05 [Bug target/97431] New: " glaubitz at physik dot fu-berlin.de 2020-10-15 0:36 ` bugdal at aerifal dot cx [this message] 2020-10-15 1:53 ` [Bug target/97431] " ysato at users dot sourceforge.jp 2020-10-15 8:03 ` glaubitz at physik dot fu-berlin.de 2020-10-15 13:39 ` olegendo at gcc dot gnu.org 2020-10-15 13:47 ` glaubitz at physik dot fu-berlin.de 2020-10-15 14:03 ` olegendo at gcc dot gnu.org 2020-10-15 14:15 ` glaubitz at physik dot fu-berlin.de 2020-10-18 18:55 ` danglin 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-97431-4-T4UmgfaChr@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).