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] [SH] [12/13/14 Regression]: libcanberra fails with 'unaligned opcodes detected in executable segment'
Date: Sun, 19 May 2024 05:48:27 +0000 [thread overview]
Message-ID: <bug-115148-4-7VBVuy6FeQ@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
Oleg Endo <olegendo at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2024-05-19
Ever confirmed|0 |1
--- Comment #3 from Oleg Endo <olegendo at gcc dot gnu.org> ---
In your attached libcanberra_la-read-vorbis.s I can spot the following
suspicious code:
.LBB70:
.loc 1 44 9 is_stmt 0
mova .L52,r0
.LVL48:
mov.b @(r0,r2),r1
extu.b r1,r1
.LVL49:
braf r1
nop
.....
.L82:
.long ca_vorbis_get_nchannels@PLT-(.LPCS10+2-.)
.L86:
.long free@PLT-(.LPCS9+2-.)
.L87:
.long ov_clear@PLT-(.LPCS11+2-.)
.align 2
.L52:
.byte .L54-.L53
.byte .L54-.L53
.byte .L51-.L53
.align 1 <<<< (1)
.L54:
.LBE70:
.LBE72: <<<< (2)
.loc 1 61 24
bra .L50
mov #-7,r9
In (1) a lookup table of 3 bytes is emitted. Because of the following ".align
1" directive, the following code at (2) will be misaligned.
Can you please try to compile with -fverbose-asm .... maybe it will give a
first hint as to where the problematic code comes from.
next prev parent reply other threads:[~2024-05-19 5:48 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 [this message]
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
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-7VBVuy6FeQ@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).