public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: rguenth@tat.physik.uni-tuebingen.de
To: gcc-gnats@gcc.gnu.org
Subject: fortran/7541: DATA statement for double precision variables does not work
Date: Thu, 08 Aug 2002 05:06:00 -0000	[thread overview]
Message-ID: <20020808115036.14220.qmail@sources.redhat.com> (raw)


>Number:         7541
>Category:       fortran
>Synopsis:       DATA statement for double precision variables does not work
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          rejects-legal
>Submitter-Id:   net
>Arrival-Date:   Thu Aug 08 04:56:02 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     rguenth@tat.physik.uni-tuebingen.de
>Release:        g77 version 3.0.5 20020403 (prerelease) (Fortran Frontend version 0.5.26 20020403 (prerelease))
>Organization:
>Environment:
SuSE linux 7.2, custom gcc 3.0.5
>Description:
g77 cannot compile NAG library due to unability to handle f.i.

      DOUBLE PRECISION FUNCTION X02AHF(X)
      DOUBLE PRECISION                 X
      DOUBLE PRECISION X02CON
      DATA X02CON /Z'4690000000000000' /
      X02AHF = X02CON
      RETURN
      END

g77 produces
bellatrix:/tmp$ g77 -c x02ahft.f 
x02ahft.f: In function `x02ahf':
x02ahft.f:13: 
         DATA X02CON /Z'4690000000000000' /
                        ^
Integer at (^) too large

the code compiles ok with intel fortran and lahey fortran. x02ahft.f from NAG library is attached.
>How-To-Repeat:
g77 -c x02ahft.f
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="x02ahft.f"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="x02ahft.f"

ICAgICAgRE9VQkxFIFBSRUNJU0lPTiBGVU5DVElPTiBYMDJBSEYoWCkKQyAgICAgTUFSSyA5IFJF
TEVBU0UuIE5BRyBDT1BZUklHSFQgMTk4MS4KQyAgICAgTUFSSyAxMS41KEY3NykgUkVWSVNFRC4g
KFNFUFQgMTk4NS4pCkMKQyAgICAgKiBNQVhJTVVNIEFSR1VNRU5UIEZPUiBTSU4gQU5EIENPUyAq
CkMgICAgIFJFVFVSTlMgVEhFIExBUkdFU1QgUE9TSVRJVkUgUkVBTCBOVU1CRVIgTUFYU0MgU1VD
SCBUSEFUCkMgICAgIFNJTihNQVhTQykgQU5EIENPUyhNQVhTQykgQ0FOIEJFIFNVQ0NFU1NGVUxM
WSBDT01QVVRFRApDICAgICBCWSBUSEUgQ09NUElMRVIgU1VQUExJRUQgU0lOIEFORCBDT1MgUk9V
VElORVMuCkMKQyAgICAgLi4gU2NhbGFyIEFyZ3VtZW50cyAuLgogICAgICBET1VCTEUgUFJFQ0lT
SU9OICAgICAgICAgICAgICAgICBYCiAgICAgIERPVUJMRSBQUkVDSVNJT04gWDAyQ09OCiAgICAg
IERBVEEgWDAyQ09OIC9aJzQ2OTAwMDAwMDAwMDAwMDAnIC8KQyAgICAgLi4gRXhlY3V0YWJsZSBT
dGF0ZW1lbnRzIC4uCiAgICAgIFgwMkFIRiA9IFgwMkNPTgogICAgICBSRVRVUk4KICAgICAgRU5E
Cg==


             reply	other threads:[~2002-08-08 11:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-08  5:06 rguenth [this message]
2002-08-08  7:37 toon
2002-08-08  9:16 Richard Guenther

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=20020808115036.14220.qmail@sources.redhat.com \
    --to=rguenth@tat.physik.uni-tuebingen.de \
    --cc=gcc-gnats@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).