public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rsandifo at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/35788] MIPS stack overflow caused by addui instruction
Date: Wed, 30 Apr 2008 21:13:00 -0000 [thread overview]
Message-ID: <20080430211214.773.qmail@sourceware.org> (raw)
In-Reply-To: <bug-35788-16000@http.gcc.gnu.org/bugzilla/>
------- Comment #9 from rsandifo at gcc dot gnu dot org 2008-04-30 21:12 -------
Sorry, I don't understand what you think the bug is. You say:
> For some reason the compiler allocates
> memory on the stack by issuing a Addui sp,sp with some negative number, however
> the negative number is only sixteen bits and therefore because the instruction
> is an add unsigned immediate this negative number gets treated like a positve
> number.
But you seem to misunderstand how the MIPS addiu instruction works.
The 16-bit immediate operand is sign-extended.
Do you actually get an execution failure?
Richard
--
rsandifo at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rsandifo at gcc dot gnu dot
| |org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35788
next prev parent reply other threads:[~2008-04-30 21:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 14:04 [Bug c++/35788] New: " derrick_chi at msn dot com
2008-04-01 14:27 ` [Bug c++/35788] " derrick_chi at msn dot com
2008-04-01 14:28 ` derrick_chi at msn dot com
2008-04-01 14:28 ` derrick_chi at msn dot com
2008-04-01 14:29 ` derrick_chi at msn dot com
2008-04-01 14:29 ` derrick_chi at msn dot com
2008-04-01 17:37 ` [Bug target/35788] " pinskia at gcc dot gnu dot org
2008-04-01 20:33 ` derrick_chi at msn dot com
2008-04-05 0:55 ` brian at dessent dot net
2008-04-30 21:13 ` rsandifo at gcc dot gnu dot org [this message]
2008-06-02 17:19 ` rsandifo at gcc dot gnu dot org
2008-06-02 21:20 ` derrick_chi at msn dot com
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=20080430211214.773.qmail@sourceware.org \
--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).