public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fm3 at os dot inf.tu-dresden.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/55940] Incorrect code for accessing parameters with 32-bit Intel hosts
Date: Tue, 15 Jan 2013 15:38:00 -0000 [thread overview]
Message-ID: <bug-55940-4-UnoylFGVcK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55940-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55940
--- Comment #7 from Frank Mehnert <fm3 at os dot inf.tu-dresden.de> 2013-01-15 15:37:43 UTC ---
Actually this looks like some mixup in the generated machine code:
VBoxHost_RTR0MemObjGetPagePhysAddr():
c1b: 8b 0f mov (%edi),%ecx
c1d: 8b 47 04 mov 0x4(%edi),%eax
c20: 8d 91 00 10 00 00 lea 0x1000(%ecx),%edx
c26: 81 fa ff 1f 00 00 cmp $0x1fff,%edx
c2c: 76 49 jbe c77
<VBoxHost_RTR0MemObjGetPagePhysAddr+0x5c>
c2e: 81 39 10 12 61 19 cmpl $0x19611210,(%ecx)
c34: 75 41 jne c77
<VBoxHost_RTR0MemObjGetPagePhysAddr+0x5c>
c36: 55 push %ebp
c37: 89 e5 mov %esp,%ebp
c39: 57 push %edi
c3a: 53 push %ebx
c3b: 8b 51 08 mov 0x8(%ecx),%edx
c3e: 8d 7d 08 lea 0x8(%ebp),%edi
c41: 8d 5a ff lea -0x1(%edx),%ebx
c44: 83 fb 07 cmp $0x7,%ebx
c47: 77 34 ja c7d
<VBoxHost_RTR0MemObjGetPagePhysAddr+0x62>
The EDI register is loaded from stack later and the two lines at 0xc1b and
0xc1d just access the EDI register before it is properly initialized.
next prev parent reply other threads:[~2013-01-15 15:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 11:17 [Bug target/55940] New: " fm3 at os dot inf.tu-dresden.de
2013-01-11 11:23 ` [Bug target/55940] " rguenth at gcc dot gnu.org
2013-01-11 11:27 ` rguenth at gcc dot gnu.org
2013-01-11 11:36 ` rguenth at gcc dot gnu.org
2013-01-15 13:53 ` fm3 at os dot inf.tu-dresden.de
2013-01-15 15:04 ` fm3 at os dot inf.tu-dresden.de
2013-01-15 15:22 ` jakub at gcc dot gnu.org
2013-01-15 15:38 ` fm3 at os dot inf.tu-dresden.de [this message]
2013-01-15 16:55 ` fm3 at os dot inf.tu-dresden.de
2013-01-15 16:56 ` fm3 at os dot inf.tu-dresden.de
2013-01-15 16:58 ` fm3 at os dot inf.tu-dresden.de
2013-01-15 17:46 ` [Bug target/55940] [4.7/4.8 Regression] " jakub at gcc dot gnu.org
2013-01-15 18:29 ` jakub at gcc dot gnu.org
2013-01-15 22:59 ` jakub at gcc dot gnu.org
2013-01-16 8:00 ` [Bug target/55940] [4.7 " jakub at gcc dot gnu.org
2013-01-16 9:01 ` fm3 at os dot inf.tu-dresden.de
2013-01-16 9:16 ` jakub at gcc dot gnu.org
2013-02-01 14:10 ` jakub at gcc dot gnu.org
2013-02-01 14:31 ` jakub 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-55940-4-UnoylFGVcK@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).