public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "olegendo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/115148] [12/13/14/15 Regression][SH]: libcanberra fails with 'unaligned opcodes detected in executable segment'
Date: Tue, 21 May 2024 08:28:00 +0000	[thread overview]
Message-ID: <bug-115148-4-WGZe4y2qU3@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 #16 from Oleg Endo <olegendo at gcc dot gnu.org> ---
(In reply to John Paul Adrian Glaubitz from comment #15)
> Created attachment 58258 [details]
> Diff of generated assembly without and with changes from PR99531
> 
> I have generated a diff that shows the difference in the generated assembly
> without and with the patch a7acb6dca941db2b1c135107dac3a34a20650d5c.

That's great, thanks a lot!

This is the problematic hunks, which causes the wrong code alignment:

.LVL108:
        bt/s    .L178           !
        mov     #-1,r0  !, <retval>
@@ -1832,36 +1830,39 @@
        .byte   .L215-.L190
        .byte   .L181-.L190
 .LVL109:
-       .align 1
-.L192:
 .LBE111:
 .LBE110:
        .loc 1 234 9
        .loc 1 234 14
+       .align 1
+.L287:
+       .align 1
+.L288:

  parent reply	other threads:[~2024-05-21  8:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-18 13:58 [Bug target/115148] New: [SH] [12/13/14 Regression]: " 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
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 [this message]
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-WGZe4y2qU3@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).