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/21950] All gfortran execution tests fail on Tru64 UNIX V4.0F: scalbn unresolved Date: Wed, 15 Jun 2005 18:53:00 -0000 [thread overview] Message-ID: <20050615185335.17016.qmail@sourceware.org> (raw) In-Reply-To: <20050607162103.21950.ro@techfak.uni-bielefeld.de> ------- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-06-15 18:53 ------- Subject: Bug 21950 CVSROOT: /cvs/gcc Module name: gcc Branch: gcc-4_0-branch Changes by: fxcoudert@gcc.gnu.org 2005-06-15 18:53:26 Modified files: libgfortran : ChangeLog c99_protos.h config.h.in configure configure.ac libgfortran/intrinsics: c99_functions.c Log message: PR libfortran/21950 * intrinsics/c99_functions.c (scalbn): Provide fallback implementation for scalbn. * c99_protos.h: Prototype for scalbn. * configure.ac: Add check for scalbn. * configure: Regenerate. * config.h.in: Regenerate. Patches: http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/ChangeLog.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.163.2.49&r2=1.163.2.50 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/c99_protos.h.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.2.14.1&r2=1.2.14.2 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/config.h.in.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.16.12.3&r2=1.16.12.4 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/configure.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.26.12.5&r2=1.26.12.6 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/configure.ac.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.20.12.5&r2=1.20.12.6 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/intrinsics/c99_functions.c.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.10.2.1&r2=1.10.2.2 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21950
next prev parent reply other threads:[~2005-06-15 18:53 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-06-07 16:21 [Bug fortran/21950] New: " gcc-bugzilla at gcc dot gnu dot org 2005-06-07 16:23 ` [Bug libfortran/21950] " pinskia at gcc dot gnu dot org 2005-06-08 13:24 ` pinskia at gcc dot gnu dot org 2005-06-08 13:34 ` ro at techfak dot uni-bielefeld dot de 2005-06-12 10:51 ` fxcoudert at gcc dot gnu dot org 2005-06-13 15:08 ` ro at techfak dot uni-bielefeld dot de 2005-06-13 15:41 ` fxcoudert at gcc dot gnu dot org 2005-06-14 23:47 ` ro at techfak dot uni-bielefeld dot de 2005-06-15 6:03 ` fxcoudert at gcc dot gnu dot org 2005-06-15 8:40 ` cvs-commit at gcc dot gnu dot org 2005-06-15 18:53 ` cvs-commit at gcc dot gnu dot org [this message] 2005-06-15 19:47 ` fxcoudert at gcc dot gnu dot org 2005-06-18 23:19 ` pinskia 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=20050615185335.17016.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: 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).