public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "glaubitz at physik dot fu-berlin.de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/115148] [SH] [12/13/14 Regression]: libcanberra fails with 'unaligned opcodes detected in executable segment' Date: Mon, 20 May 2024 21:12:36 +0000 [thread overview] Message-ID: <bug-115148-4-pfSkMfUuas@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115148-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115148 --- Comment #13 from John Paul Adrian Glaubitz <glaubitz at physik dot fu-berlin.de> --- I can even confirm that reverting a7acb6dca941db2b1c135107dac3a34a20650d5c (with some minor merge adjustments) on current git master fixes the problem for me.
next prev parent reply other threads:[~2024-05-20 21:12 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-18 13:58 [Bug target/115148] New: " glaubitz at physik dot fu-berlin.de 2024-05-18 14:02 ` [Bug target/115148] " glaubitz at physik dot fu-berlin.de 2024-05-18 14:20 ` glaubitz at physik dot fu-berlin.de 2024-05-19 5:48 ` olegendo at gcc dot gnu.org 2024-05-19 11:24 ` glaubitz at physik dot fu-berlin.de 2024-05-19 13:46 ` olegendo at gcc dot gnu.org 2024-05-19 13:52 ` glaubitz at physik dot fu-berlin.de 2024-05-19 14:13 ` olegendo at gcc dot gnu.org 2024-05-19 15:20 ` olegendo at gcc dot gnu.org 2024-05-19 15:21 ` olegendo at gcc dot gnu.org 2024-05-20 7:52 ` glaubitz at physik dot fu-berlin.de 2024-05-20 7:57 ` olegendo at gcc dot gnu.org 2024-05-20 20:40 ` glaubitz at physik dot fu-berlin.de 2024-05-20 21:12 ` glaubitz at physik dot fu-berlin.de [this message] 2024-05-20 23:20 ` olegendo at gcc dot gnu.org 2024-05-21 6:35 ` [Bug target/115148] [12/13/14/15 Regression][SH]: " rguenth at gcc dot gnu.org 2024-05-21 7:39 ` glaubitz at physik dot fu-berlin.de 2024-05-21 8:28 ` olegendo at gcc dot gnu.org 2024-06-20 9:15 ` rguenth 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-115148-4-pfSkMfUuas@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).