public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/23815] Add -byteswapio flag
Date: Sat, 05 Nov 2005 22:21:00 -0000	[thread overview]
Message-ID: <20051105222119.5633.qmail@sourceware.org> (raw)
In-Reply-To: <bug-23815-7128@http.gcc.gnu.org/bugzilla/>



------- Comment #11 from tkoenig at gcc dot gnu dot org  2005-11-05 22:21 -------
OK, for the interface...

My suggestion would be to have three levels of supplying this value (ifort
has five or six :-)

First, an option to supply to the compiler.  This could be
-fconvert=big_endian
-fconvert=little_endian
-fconvert=native (the default)

and maybe, at a later date,
-fconvert=vax_d
-fconvert=ibm_360.

This would be valid for all the units.

With this option alone, it would not be possible to write a conversion
program, so we need something else.

This could be overridden by a CONVERT="BIG_ENDIAN" etc. in the OPEN statement.

This, in turn, could be overridden by environment variables in the format

GFORTRAN_CONVERT_BIG_ENDIAN=10,20,30,40
GFORTRAN_CONVERT_LITTLE_ENDIAN=11,21,31,41

Agreed?

It would probably best to implement the compiler swith as selecting a
library at runtime.  I'll leave that to a later date :-)

If anybody knows how to set an environment variable in a dejagnu
testcase, please tell :-)


-- 


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


  parent reply	other threads:[~2005-11-05 22:21 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-23815-7128@http.gcc.gnu.org/bugzilla/>
2005-10-11 13:25 ` tobi at gcc dot gnu dot org
2005-10-11 18:40 ` tkoenig at gcc dot gnu dot org
2005-10-11 19:01 ` Tobias dot Schlueter at physik dot uni-muenchen dot de
2005-10-11 19:20 ` rrr6399 at futuretek dot com
2005-10-11 19:37 ` tkoenig at gcc dot gnu dot org
2005-11-02 17:16 ` pinskia at gcc dot gnu dot org
2005-11-02 18:17 ` rrr6399 at futuretek dot com
2005-11-02 21:20 ` tkoenig at gcc dot gnu dot org
2005-11-05 22:21 ` tkoenig at gcc dot gnu dot org [this message]
2005-11-10 22:39 ` tkoenig at gcc dot gnu dot org
2005-11-10 22:53 ` tkoenig at gcc dot gnu dot org
2005-11-11  4:52 ` kargl at gcc dot gnu dot org
2005-11-11 13:26 ` rrr6399 at futuretek dot com
2005-11-11 23:53 ` tkoenig at gcc dot gnu dot org
2005-11-12  0:02 ` tkoenig at gcc dot gnu dot org
2005-11-18 21:17 ` tkoenig at gcc dot gnu dot org
2005-11-27 22:15 ` tkoenig at gcc dot gnu dot org
2005-11-27 22:27 ` tkoenig at gcc dot gnu dot org
2005-11-27 22:42 ` sgk at troutmask dot apl dot washington dot edu
2005-12-06 21:45 ` tkoenig at gcc dot gnu dot org
2005-12-10 13:09 ` tkoenig at gcc dot gnu dot org
2005-12-10 20:02 ` tkoenig at gcc dot gnu dot org
2005-12-10 20:12 ` tkoenig at gcc dot gnu dot org
2005-12-13 21:11 ` tkoenig at gcc dot gnu dot org
2006-01-09 22:53 ` tkoenig at gcc dot gnu dot org
2006-01-15 21:07 ` tkoenig at gcc dot gnu dot org
2006-01-27 20:40 ` tkoenig at gcc dot gnu dot org
2006-02-06 20:12 ` tkoenig at gcc dot gnu dot org
2006-02-08 20:14 ` tkoenig at gcc dot gnu dot org
2006-02-08 20:15 ` tkoenig at gcc dot gnu dot org
2006-02-09 15:12 ` tobi at gcc dot gnu dot org
2006-02-09 20:03 ` tkoenig at gcc dot gnu dot org
2005-09-11  5:14 [Bug fortran/23815] New: " rrr6399 at futuretek dot com
2005-09-12 14:29 ` [Bug fortran/23815] " pinskia at gcc dot gnu dot org
2005-09-12 19:22 ` falk at debian 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=20051105222119.5633.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).