public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bugzilla-gcc at thewrittenword dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/19144] SPARC back-end bug
Date: Fri, 24 Dec 2004 02:03:00 -0000 [thread overview]
Message-ID: <20041224020311.32583.qmail@sourceware.org> (raw)
In-Reply-To: <20041224015246.19144.bugzilla-gcc@thewrittenword.com>
------- Additional Comments From bugzilla-gcc at thewrittenword dot com 2004-12-24 02:03 -------
Ok, I ran diff on both .s files (id #7816 v id #7818) and found the following:
@@ -199,8 +199,8 @@
cmp %g1, 0
bne .LL9
nop
- add %fp, -80, %g1
- add %fp, -84, %o5
* + add %fp, -72, %g1
+ add %fp, -80, %o5
ld [%fp-20], %o0
mov %g1, %o1
mov %o5, %o2
If you review the diff of the .s files between #7816 and #7818, the
numeric differences are the same except for the line with the '*'
above. I modified the .s file and changed -72 to -76 (diff of four
from -80 on the next line) and it worked (patch below)!
--- id7816/kurlcompletion.s Thu Dec 23 19:20:59 2004
+++ kurlcompletion.s Thu Dec 23 19:40:52 2004
@@ -199,7 +199,7 @@
cmp %g1, 0
bne .LL9
nop
- add %fp, -72, %g1
+ add %fp, -76, %g1
ld [%fp-20], %o0
mov %g1, %o1
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19144
next prev parent reply other threads:[~2004-12-24 2:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-24 1:52 [Bug c++/19144] New: SPARC backend bug bugzilla-gcc at thewrittenword dot com
2004-12-24 1:54 ` [Bug c++/19144] " bugzilla-gcc at thewrittenword dot com
2004-12-24 1:55 ` bugzilla-gcc at thewrittenword dot com
2004-12-24 1:56 ` bugzilla-gcc at thewrittenword dot com
2004-12-24 1:57 ` [Bug target/19144] SPARC back-end bug pinskia at gcc dot gnu dot org
2004-12-24 1:57 ` [Bug c++/19144] SPARC backend bug bugzilla-gcc at thewrittenword dot com
2004-12-24 1:58 ` [Bug target/19144] SPARC back-end bug bugzilla-gcc at thewrittenword dot com
2004-12-24 1:59 ` bugzilla-gcc at thewrittenword dot com
2004-12-24 2:03 ` bugzilla-gcc at thewrittenword dot com [this message]
2004-12-24 2:04 ` bugzilla-gcc at thewrittenword dot com
2004-12-24 2:09 ` pinskia at gcc dot gnu dot org
2004-12-24 2:59 ` bugzilla-gcc at thewrittenword dot com
2004-12-24 6:36 ` [Bug target/19144] miscompilation KDE 3.3.2 ebotcazou at gcc dot gnu dot org
2004-12-24 7:00 ` bugzilla-gcc at thewrittenword dot com
2004-12-24 7:00 ` bugzilla-gcc at thewrittenword dot com
2004-12-24 7:06 ` bugzilla-gcc at thewrittenword dot com
2004-12-24 7:07 ` bugzilla-gcc at thewrittenword dot com
2004-12-24 8:45 ` bugzilla-gcc at thewrittenword dot com
2004-12-24 17:18 ` bugzilla-gcc at thewrittenword dot com
2004-12-24 17:34 ` bugzilla-gcc at thewrittenword dot com
2004-12-24 18:50 ` bugzilla-gcc at thewrittenword dot com
2004-12-24 18:52 ` pinskia at gcc dot gnu dot 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=20041224020311.32583.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).