public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "martinez at nsup dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug math/15194] New: pow leads to segmentation fault when called after fesetround(FE_UPWARD);
Date: Mon, 25 Feb 2013 16:49:00 -0000 [thread overview]
Message-ID: <bug-15194-131@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=15194
Bug #: 15194
Summary: pow leads to segmentation fault when called after
fesetround(FE_UPWARD);
Product: glibc
Version: 2.18
Status: NEW
Severity: normal
Priority: P2
Component: math
AssignedTo: unassigned@sourceware.org
ReportedBy: martinez@nsup.org
Classification: Unclassified
The following code leads to segmentation fault with the current git version of
GNU libc (and that is the case at least from 2.15).
#include <math.h>
#include <fenv.h>
int
main()
{
double x = 2.8532681940591602;
fesetround(FE_UPWARD);
pow(x, 4);
}
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2013-02-25 16:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 16:49 martinez at nsup dot org [this message]
2013-02-25 19:53 ` [Bug math/15194] " bagnara at cs dot unipr.it
2013-02-25 23:46 ` martinez at nsup dot org
2013-02-26 0:57 ` joseph at codesourcery dot com
2013-02-26 8:50 ` schwab@linux-m68k.org
2013-02-26 15:23 ` martinez at nsup dot org
2013-02-26 15:29 ` aj at suse dot de
2013-02-26 15:32 ` martinez at nsup dot org
2013-02-26 15:33 ` martinez at nsup dot org
2014-06-13 18:47 ` fweimer at redhat dot com
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=bug-15194-131@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.org \
/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).