public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mgilbert at airborne dot nrl dot navy dot mil" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/19443] New: log10 statement does not work properly in gfortran
Date: Fri, 14 Jan 2005 12:57:00 -0000	[thread overview]
Message-ID: <20050114125627.19443.mgilbert@airborne.nrl.navy.mil> (raw)

The log10 operator in gfortran (cygwin build 20041213) does not work properly if
the statement is operated on a variable, but it works fine when operating on a
constant.  The plain log statement works fine regardless.  If the following
program is executed, one can observer that log for the two methods generates the
same value, but log10 using the different methods produces different results. 
The 10*log10(tst) appears to generate -Infinity, where it should generate -50.

program test
  implicit none
  real :: tst
  
  tst=1e-5
  write(*,*) 10*log(1e-5), 10*log(tst)
  write(*,*) 10*log10(1e-5), 10*log10(tst)
end program test

-- 
           Summary: log10 statement does not work properly in gfortran
           Product: gcc
           Version: 4.0.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: mgilbert at airborne dot nrl dot navy dot mil
                CC: gcc-bugs at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19443


             reply	other threads:[~2005-01-14 12:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-14 12:57 mgilbert at airborne dot nrl dot navy dot mil [this message]
2005-01-14 13:05 ` [Bug fortran/19443] " pinskia at gcc dot gnu dot org
2005-01-14 13:20 ` mgilbert at airborne dot nrl dot navy dot mil
2005-01-14 13:25 ` pinskia at gcc dot gnu dot org
2005-01-14 13:35 ` mgilbert at airborne dot nrl dot navy dot mil
2005-01-14 13:38 ` pinskia at gcc dot gnu dot org
2005-01-14 13:42 ` mgilbert at airborne dot nrl dot navy dot mil
2005-01-14 13:51 ` pinskia at gcc dot gnu dot org
2005-01-14 16:51 ` mgilbert at airborne dot nrl dot navy dot mil
2005-01-17 22:59 ` tobi at gcc dot gnu dot org
2005-01-17 23:01 ` tobi at gcc dot gnu dot org
2005-01-25  9:45 ` paulthomas2 at wanadoo dot fr
2005-01-31  4:38 ` sgk at troutmask dot apl dot washington dot edu
2005-02-07 22:52 ` tobi at gcc dot gnu dot org
2005-02-07 23:09 ` tobi at gcc dot gnu dot org
2005-03-04 18:01 ` mgilbert at airborne dot nrl dot navy dot mil
2005-03-13 17:28 ` tobi 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=20050114125627.19443.mgilbert@airborne.nrl.navy.mil \
    --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).