public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bruno at clisp dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/4359] New: the __freadable function is not compatible with Solaris Date: Fri, 13 Apr 2007 22:04:00 -0000 [thread overview] Message-ID: <20070413230421.4359.bruno@clisp.org> (raw) The comments in <stdio_ext.h> indicate that the functions declared in this file are intended to be Solaris compatible. However, __freadable is not. Attached program prints on Solaris: Initial state for write-only stream: 0 1 Initial state for read-only stream: 1 0 Initial state for read-write stream: 0 0 Initial state for read-write stream: 0 0 And on a glibc system: Initial state for write-only stream: 1 1 Initial state for read-only stream: 1 0 Initial state for read-write stream: 1 0 Initial state for read-write stream: 1 0 -- Summary: the __freadable function is not compatible with Solaris Product: glibc Version: 2.3.6 Status: NEW Severity: normal Priority: P2 Component: libc AssignedTo: drepper at redhat dot com ReportedBy: bruno at clisp dot org CC: glibc-bugs at sources dot redhat dot com GCC build triplet: i586-suse-linux GCC host triplet: i586-suse-linux GCC target triplet: i586-suse-linux http://sourceware.org/bugzilla/show_bug.cgi?id=4359 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2007-04-13 22:04 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-04-13 22:04 bruno at clisp dot org [this message] 2007-04-13 22:05 ` [Bug libc/4359] " bruno at clisp dot org 2007-04-13 22:07 ` [Bug libc/4359] the __freading " bruno at clisp dot org 2007-10-13 7:21 ` drepper at redhat dot com 2007-10-13 11:13 ` bruno at clisp 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=20070413230421.4359.bruno@clisp.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: linkBe 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).