public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <sourceware-bugzilla@sources.redhat.com>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/730] libio fmemopen broken
Date: Wed, 16 Feb 2005 09:45:00 -0000 [thread overview]
Message-ID: <20050216094527.10232.qmail@sourceware.org> (raw)
In-Reply-To: <20050216043241.730.roland@gnu.org>
------- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-02-16 09:45 -------
Subject: Bug 730
CVSROOT: /cvs/glibc
Module name: libc
Branch: glibc-2_3-branch
Changes by: roland@sources.redhat.com 2005-02-16 09:45:11
Modified files:
libio : fmemopen.c
stdio-common : Makefile
Log message:
2005-01-05 Ulrich Drepper <drepper@redhat.com>
[BZ #730]
* libio/iofopncook.c (_IO_cookie_seekoff): Define. Mark offset as
invalid to disable optimizations in fileops which won't work here.
(_IO_cookie_jumps): Use it.
(_IO_old_cookie_jumps): Likewise.
* libio/fmemopen.c (fmemopen_seek): Result must be returned in *P,
not the return value.
* stdio-common/Makefile (tests): Add tst-fmemopen2.
* stdio-common/tst-fmemopen2.c: New file.
Patches:
http://sources.redhat.com/cgi-bin/cvsweb.cgi/libc/libio/fmemopen.c.diff?cvsroot=glibc&only_with_tag=glibc-2_3-branch&r1=1.8&r2=1.8.4.1
http://sources.redhat.com/cgi-bin/cvsweb.cgi/libc/stdio-common/Makefile.diff?cvsroot=glibc&only_with_tag=glibc-2_3-branch&r1=1.90&r2=1.90.4.1
--
http://sources.redhat.com/bugzilla/show_bug.cgi?id=730
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2005-02-16 9:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-16 4:32 [Bug libc/730] New: " roland at gnu dot org
2005-02-16 9:45 ` cvs-commit at gcc dot gnu dot org [this message]
2005-02-16 9:46 ` [Bug libc/730] " cvs-commit at gcc dot gnu dot org
2005-02-16 9:46 ` cvs-commit at gcc dot gnu dot org
2005-04-05 23:59 ` roland at 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=20050216094527.10232.qmail@sourceware.org \
--to=sourceware-bugzilla@sources.redhat.com \
--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).