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/16137] Fortran compiler unable to produce executables as libfortran depends on C99 math functions Date: Sun, 26 Sep 2004 14:52:00 -0000 [thread overview] Message-ID: <20040926145207.29700.qmail@sourceware.org> (raw) In-Reply-To: <20040622111044.16137.ebotcazou@gcc.gnu.org> ------- Additional Comments From cvs-commit at gcc dot gnu dot org 2004-09-26 14:52 ------- Subject: Bug 16137 CVSROOT: /cvs/gcc Module name: gcc Changes by: tobi@gcc.gnu.org 2004-09-26 14:52:04 Modified files: libgfortran : ChangeLog config.h.in configure.ac configure libgfortran/intrinsics: c99_functions.c Log message: PR libfortran/16137 * config.h.in (HAVE_POWF): Undefine. * configure.ac: Check for 'powf' in library. * configure: Regenerate. * intrinsics/c99_functions.c (powf): New function. Patches: http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/ChangeLog.diff?cvsroot=gcc&r1=1.93&r2=1.94 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/config.h.in.diff?cvsroot=gcc&r1=1.8&r2=1.9 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/configure.ac.diff?cvsroot=gcc&r1=1.10&r2=1.11 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/configure.diff?cvsroot=gcc&r1=1.14&r2=1.15 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/intrinsics/c99_functions.c.diff?cvsroot=gcc&r1=1.4&r2=1.5 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16137
next prev parent reply other threads:[~2004-09-26 14:52 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-06-22 11:10 [Bug libfortran/16137] New: Fortran compiler unable to produce executables ebotcazou at gcc dot gnu dot org 2004-06-22 15:34 ` [Bug libfortran/16137] Fortran compiler unable to produce executables as libfortran depends on C99 math functions pinskia at gcc dot gnu dot org 2004-06-23 13:18 ` ro at techfak dot uni-bielefeld dot de 2004-06-24 5:09 ` sgk at troutmask dot apl dot washington dot edu 2004-06-24 17:48 ` ro at techfak dot uni-bielefeld dot de 2004-08-03 13:28 ` cvs-commit at gcc dot gnu dot org 2004-08-03 14:46 ` pinskia at gcc dot gnu dot org 2004-08-23 13:44 ` tobi at gcc dot gnu dot org 2004-08-31 6:08 ` pinskia at gcc dot gnu dot org 2004-09-08 7:31 ` ebotcazou at gcc dot gnu dot org 2004-09-26 7:11 ` ebotcazou at gcc dot gnu dot org 2004-09-26 14:17 ` pinskia at gcc dot gnu dot org 2004-09-26 14:52 ` cvs-commit at gcc dot gnu dot org [this message] 2004-09-26 14:54 ` tobi at gcc dot gnu dot org 2004-09-26 15:15 ` 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=20040926145207.29700.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).