public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/933] MIPS (n)64 syscall() implemented incorrectly
Date: Fri, 16 Sep 2005 12:22:00 -0000	[thread overview]
Message-ID: <20050916122126.9128.qmail@sourceware.org> (raw)
In-Reply-To: <20050505192350.933.macro@linux-mips.org>


------- Additional Comments From cvs-commit at gcc dot gnu dot org  2005-09-16 12:21 -------
Subject: Bug 933

CVSROOT:	/cvs/glibc
Module name:	libc
Changes by:	aj@sources.redhat.com	2005-09-16 12:21:01

Modified files:
	sysdeps/unix/sysv/linux/mips/mips64/n64: ioctl.S 
	sysdeps/unix/sysv/linux/mips/mips64: syscall.S 
	sysdeps/unix/sysv/linux/mips: brk.c 
	.              : ChangeLog 

Log message:
	2005-09-16  Maciej W. Rozycki  <macro@linux-mips.org>
	
	[BZ #933]
	* sysdeps/unix/sysv/linux/mips/brk.c (__brk): Load the number of
	the syscall immediately before invocation.
	* sysdeps/unix/sysv/linux/mips/mips64/n64/ioctl.S (__ioctl): Likewise.
	* sysdeps/unix/sysv/linux/mips/mips64/syscall.S (syscall): Likewise.
	
	* sysdeps/unix/sysv/linux/mips/mips64/n64/ioctl.S (__ioctl): Use
	macros to handle GP.
	* sysdeps/unix/sysv/linux/mips/mips64/syscall.S (syscall):
	Likewise.  Update inaccurate comments.

Patches:
http://sources.redhat.com/cgi-bin/cvsweb.cgi/libc/sysdeps/unix/sysv/linux/mips/mips64/n64/ioctl.S.diff?cvsroot=glibc&r1=1.2&r2=1.3
http://sources.redhat.com/cgi-bin/cvsweb.cgi/libc/sysdeps/unix/sysv/linux/mips/mips64/syscall.S.diff?cvsroot=glibc&r1=1.1&r2=1.2
http://sources.redhat.com/cgi-bin/cvsweb.cgi/libc/sysdeps/unix/sysv/linux/mips/brk.c.diff?cvsroot=glibc&r1=1.2&r2=1.3
http://sources.redhat.com/cgi-bin/cvsweb.cgi/libc/ChangeLog.diff?cvsroot=glibc&r1=1.9525&r2=1.9526



-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=933

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


      parent reply	other threads:[~2005-09-16 12:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-05 19:23 [Bug libc/933] New: " macro at linux-mips dot org
2005-05-06 15:18 ` [Bug libc/933] " macro at linux-mips dot org
2005-05-06 15:19 ` macro at linux-mips dot org
2005-06-01 14:38 ` gotom at debian dot or dot jp
2005-07-01 16:06 ` macro at linux-mips dot org
2005-09-16 12:21 ` aj at suse dot de
2005-09-16 12:22 ` cvs-commit at gcc dot gnu dot org [this message]

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=20050916122126.9128.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.com \
    /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).