From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <glibc-bugs-return-11620-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Received: (qmail 1427 invoked by alias); 30 Aug 2010 20:29:50 -0000
Received: (qmail 1384 invoked by uid 48); 30 Aug 2010 20:29:38 -0000
Date: Mon, 30 Aug 2010 20:33:00 -0000
From: "jim at meyering dot net" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Message-ID: <20100830202938.11959.jim@meyering.net>
Reply-To: sourceware-bugzilla@sourceware.org
Subject: [Bug libc/11959] New: fwrite must not be declared with the warn_unused_result attribute
X-Bugzilla-Reason: CC
Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <glibc-bugs.sourceware.org>
List-Subscribe: <mailto:glibc-bugs-subscribe@sourceware.org>
List-Post: <mailto:glibc-bugs@sourceware.org>
List-Help: <mailto:glibc-bugs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: glibc-bugs-owner@sourceware.org
X-SW-Source: 2010-08/txt/msg00109.txt.bz2

The use of the warn_unused_result attribute in the declaration of fwrite is
undesirable, since it is perfectly legitimate to use fwrite without inspecting
its return value.  In that case, one can still detect failure via ferror.
That libc declares fwrite with this attribute causes inordinate trouble for
those who try to avoid gcc warnings about this attribute.

Patch below.

-- 
           Summary: fwrite must not be declared with the warn_unused_result
                    attribute
           Product: glibc
           Version: 2.13
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: drepper at redhat dot com
        ReportedBy: jim at meyering dot net
                CC: glibc-bugs at sources dot redhat dot com


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

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