public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/19302] intrinsic_nearest.f90 fails
Date: Tue, 22 Feb 2005 00:54:00 -0000 [thread overview]
Message-ID: <20050221213939.6232.qmail@sourceware.org> (raw)
In-Reply-To: <20050106232426.19302.coudert@clipper.ens.fr>
------- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-02-21 21:39 -------
Subject: Bug 19302
CVSROOT: /cvs/gcc
Module name: gcc
Changes by: ebotcazou@gcc.gnu.org 2005-02-21 21:39:33
Modified files:
libgfortran : ChangeLog
libgfortran/intrinsics: c99_functions.c
Log message:
PR libfortran/19302
* intrinsics/c99_functions.c (nextafterf): Special-case infinite
numbers.
Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/ChangeLog.diff?cvsroot=gcc&r1=1.160&r2=1.161
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/intrinsics/c99_functions.c.diff?cvsroot=gcc&r1=1.9&r2=1.10
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19302
next prev parent reply other threads:[~2005-02-21 21:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 23:24 [Bug fortran/19302] New: nearest test case fails coudert at clipper dot ens dot fr
2005-01-06 23:28 ` [Bug fortran/19302] " pinskia at gcc dot gnu dot org
2005-01-07 0:32 ` [Bug fortran/19302] intrinsic_nearest.f90 fails ebotcazou at gcc dot gnu dot org
2005-01-07 0:33 ` ebotcazou at gcc dot gnu dot org
2005-01-07 10:57 ` Thomas dot Koenig at online dot de
2005-01-07 12:30 ` coudert at clipper dot ens dot fr
2005-01-24 7:30 ` coudert at clipper dot ens dot fr
2005-02-12 22:25 ` ebotcazou at gcc dot gnu dot org
2005-02-20 15:52 ` [Bug libfortran/19302] " ebotcazou at gcc dot gnu dot org
2005-02-22 0:54 ` cvs-commit at gcc dot gnu dot org [this message]
2005-02-22 1:15 ` ebotcazou at gcc dot gnu 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=20050221213939.6232.qmail@sourceware.org \
--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: 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).