public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/62188] Array bounds overrun in bessel_yn_r4/8/16 and other functions Date: Wed, 20 Aug 2014 16:30:00 -0000 [thread overview] Message-ID: <bug-62188-4-9KoNb9WESi@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-62188-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62188 kargl at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #7 from kargl at gcc dot gnu.org --- (In reply to Dominik Vogt from comment #3) > (In reply to kargl from comment #1) > > I assume you found this by using a libc with > > a malloc that has buffer overflow detection. > > Actually, no. We inspected the function manually looking for the > cause of a test FAIL of bessel_7.f90 and just stumbled across it. Ah, bessel_7.f90. This test has some tolerances that are at the very edge of numerical accuracy. If your underlying libm implementation of yn is poor, you'll get FAIL[ures]. > > I'll commit this later. > > Great. Committed to trunk and all open branches. Thanks for the bug report.
next prev parent reply other threads:[~2014-08-20 16:30 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-08-19 13:48 [Bug libfortran/62188] New: " vogt at linux dot vnet.ibm.com 2014-08-19 16:54 ` [Bug libfortran/62188] " kargl at gcc dot gnu.org 2014-08-20 7:03 ` vogt at linux dot vnet.ibm.com 2014-08-20 16:19 ` kargl at gcc dot gnu.org 2014-08-20 16:22 ` kargl at gcc dot gnu.org 2014-08-20 16:24 ` kargl at gcc dot gnu.org 2014-08-20 16:30 ` kargl at gcc dot gnu.org [this message] 2014-08-26 13:08 ` burnus at gcc dot gnu.org 2014-08-26 14:52 ` sgk at troutmask dot apl.washington.edu 2014-08-26 17:54 ` sgk at troutmask dot apl.washington.edu 2014-08-26 18:14 ` sgk at troutmask dot apl.washington.edu
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-62188-4-9KoNb9WESi@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: 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).