From: "Reese Faucette" <reese@myri.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] IA64 strncpy in 2.2.4-30 - bug and patch
Date: Wed, 06 Nov 2002 00:39:27 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805337@msgid-missing> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 566 bytes --]
Hi,
I opened a bug with RedHat about a problem with strncpy() in glibc-2.2.4-30 on IA64, see https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=76952, but I've been told you folks are really the ones to talk to.
The bug report contains a testcase illustrating the problem, and also a patch. In short, the recovery code is busted, even after the patch from David Mosberger. Attached is a copy of the patch from the bug report.
I have a testcase which exercizes both the recovery3 and recovery4 paths if you're interested.
Regards,
-reese faucette
[-- Attachment #1.2: Type: text/html, Size: 1381 bytes --]
[-- Attachment #2: strncpy.patch --]
[-- Type: application/octet-stream, Size: 437 bytes --]
--- strncpy.S Thu Oct 31 15:19:46 2002
+++ new/strncpy.S Thu Oct 31 17:11:34 2002
@@ -214,11 +214,11 @@
ld8 r[0] = [tmp]
br.cond.sptk .back2
.recovery3:
- add tmp = -MEMLAT * 8, src ;;
+ add tmp = -(MEMLAT+1) * 8, src ;;
ld8 r[MEMLAT] = [tmp]
br.cond.sptk .back3
.recovery4:
- add tmp = -(MEMLAT - 1) * 8, src ;;
+ add tmp = -(MEMLAT) * 8, src ;;
ld8 r[MEMLAT - 1] = [tmp]
br.cond.sptk .back4
END(strncpy)
next reply other threads:[~2002-11-06 0:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-06 0:39 Reese Faucette [this message]
2002-11-06 0:43 ` [Linux-ia64] IA64 strncpy in 2.2.4-30 - bug and patch Chen, Kenneth W
2002-11-07 2:56 ` Chen, Kenneth W
2002-11-07 19:10 ` Chen, Kenneth W
2002-11-08 11:06 ` Andreas Schwab
2002-11-08 11:31 ` Reese Faucette
2002-11-19 16:19 ` Randolph Chung
2002-11-19 18:35 ` Chen, Kenneth W
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=marc-linux-ia64-105590709805337@msgid-missing \
--to=reese@myri.com \
--cc=linux-ia64@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.