public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/94119] MIPS: Invalid use of branch delay slots leading to corrupt jump
Date: Wed, 11 Mar 2020 16:27:52 +0000 [thread overview]
Message-ID: <bug-94119-4-b0bwkgZkty@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94119-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94119
--- Comment #3 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> The addiu s0,s0,0 instruction must only be issued once but instead is in
> several places. This leads to an invalid call at 9c.
Duplicating the instruction is not a problem per se if it is executed only once
on any execution path. Are you sure that the problem is for the call at 9c?
> 8c: 3c100000 lui s0,0x0
> 8c: R_MIPS_HI16 memcmp_
> 90: 24060006 li a2,6
> 94: 27a50014 addiu a1,sp,20
> 98: 26100000 addiu s0,s0,0
> 98: R_MIPS_LO16 memcmp_
> 9c: 0200f809 jalr s0
AFAICS there is only one "addiu s0,s0,0" executed after the "lui s0,0x0" in
this basic block. Doesn't the problem occur for the call in the following
basic block instead?
next prev parent reply other threads:[~2020-03-11 16:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 10:44 [Bug c/94119] New: " d.dorau at avm dot de
2020-03-11 13:47 ` [Bug rtl-optimization/94119] " ebotcazou at gcc dot gnu.org
2020-03-11 14:43 ` d.dorau at avm dot de
2020-03-11 16:27 ` ebotcazou at gcc dot gnu.org [this message]
2020-03-12 8:51 ` d.dorau at avm dot de
2020-03-12 11:31 ` [Bug rtl-optimization/94119] [8/9/10 regression] invalid filling of branch delay slots leads " ebotcazou at gcc dot gnu.org
2020-03-12 11:31 ` ebotcazou at gcc dot gnu.org
2020-03-13 9:09 ` marxin at gcc dot gnu.org
2020-03-13 9:10 ` marxin at gcc dot gnu.org
2020-03-13 9:12 ` marxin at gcc dot gnu.org
2020-03-13 9:14 ` ebotcazou at gcc dot gnu.org
2020-03-13 16:23 ` d.dorau at avm dot de
2020-03-13 17:06 ` ebotcazou 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-94119-4-b0bwkgZkty@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).