From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5344 invoked by alias); 30 Jul 2008 15:02:50 -0000 Received: (qmail 4011 invoked by uid 48); 30 Jul 2008 15:01:23 -0000 Date: Wed, 30 Jul 2008 15:02:00 -0000 From: "mtk dot manpages at gmail dot com" To: glibc-bugs@sources.redhat.com Message-ID: <20080730150120.6787.mtk.manpages@gmail.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug math/6787] New: exp10() does not consistently set errno X-Bugzilla-Reason: CC Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org X-SW-Source: 2008-07/txt/msg00143.txt.bz2 exp10() correctly raises exceptions for overflow and underflow. However, errno is only set to ERANGE for the overflow case. For underflow, it is not set. It should also be set to ERANGE in the latter case. Note also that exp10() is inconsistent with exp2() and exp(), both of which always set errno for bother underflow and overflow. Background: On error, many glibc math functions both set errno and raise an exception (fetestexcept(3)). For example, the following function all do this: acos(), asin(), cosh(), sinh(), acosh(), asinh(), exp(), exp2(), ldexp(), log(), log10(), log2(). However, there is much inconsistency. Some functions raise an exception, but don't set errno. Some functions set errno for some errors, but not others. A few set errno, but don't raise an exception. This series of bug reports documents deviations from what I consider the ideal: all functions should BOTH set errno AND raise an exception for all errors. All of these reports relate to tests on glibc 2.8 (as provided by SUSE 11.0). -- Summary: exp10() does not consistently set errno Product: glibc Version: unspecified Status: NEW Severity: normal Priority: P2 Component: math AssignedTo: aj at suse dot de ReportedBy: mtk dot manpages at gmail dot com CC: glibc-bugs at sources dot redhat dot com http://sourceware.org/bugzilla/show_bug.cgi?id=6787 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.