public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/31917] GFORTRAN_CONVERT_UNIT is ignored
Date: Mon, 14 May 2007 08:38:00 -0000	[thread overview]
Message-ID: <20070514083810.21859.qmail@sourceware.org> (raw)
In-Reply-To: <bug-31917-13404@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from burnus at gcc dot gnu dot org  2007-05-14 09:38 -------
> GFORTRAN_CONVERT_UNIT set to ""
> default:"BIG_ENDIAN"

> GFORTRAN_CONVERT_UNIT set to "LITTLE_ENDIAN"
> default:"BIG_ENDIAN"

> However I am confused about what to expect from this test:
> should the default change or not?

I would expect that the default changes depending on the environment variable.
But according to the documentation all should change:

"Note that the values specified via the GFORTRAN_CONVERT_UNIT environment
variable will override the CONVERT specifier in the open statement. This is to
give control over data formats to users who do not have the source code of
their program available."

Documentation "bug": Such a statement is missing for GFORTRAN_CONVERT_UNIT
section; it is only present in the CONVERT specifier section:
http://gcc.gnu.org/onlinedocs/gfortran/CONVERT-specifier.html


-- 


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


  parent reply	other threads:[~2007-05-14  8:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-14  7:04 [Bug fortran/31917] New: " burnus at gcc dot gnu dot org
2007-05-14  7:52 ` [Bug fortran/31917] " dominiq at lps dot ens dot fr
2007-05-14  8:38 ` burnus at gcc dot gnu dot org [this message]
2007-05-14 19:07 ` patchapp at dberlin dot org
2007-05-14 19:09 ` burnus at gcc dot gnu dot org
2007-05-17  8:39 ` burnus at gcc dot gnu dot org
2007-05-22 20:04 ` [Bug fortran/31917] [4.2, 4.1 only] " tkoenig at gcc dot gnu dot org
2007-05-23  7:44 ` [Bug fortran/31917] [4.1 " burnus at gcc dot gnu dot org
2007-05-23  7:45 ` burnus 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=20070514083810.21859.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).