public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "milan at cmm dot ki dot si" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/30689] equivalence modifies common block
Date: Sun, 04 Feb 2007 00:13:00 -0000	[thread overview]
Message-ID: <20070204001331.28354.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30689-3791@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from milan at cmm dot ki dot si  2007-02-04 00:13 -------
OK, maybe gfortran is right. It doesn't make much sense to me, but this is what
I found from wikipedia links in its fortran entry:

"Variables and arrays in common blocks can appear in EQUIVALENCE statements but
this has the effect of bringing all the associated items into the block. They
can be used to extend the contents of the block upwards, subject to the rules
for common block length, but not downwards."

So it seems that equivalence can change the size of common block :-(
In the next statement it also says that equivalence is mainly used to brake the
rules of fortran :-? So I am basically willing to give up on this and never
touch any equivalence stuff in the future :-)


-- 


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


  parent reply	other threads:[~2007-02-04  0:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-03 11:31 [Bug fortran/30689] New: " milan at cmm dot ki dot si
2007-02-03 16:11 ` [Bug fortran/30689] " pault at gcc dot gnu dot org
2007-02-03 19:59 ` kargl at gcc dot gnu dot org
2007-02-03 23:52 ` milan at cmm dot ki dot si
2007-02-04  0:13 ` milan at cmm dot ki dot si [this message]
2007-02-04  2:27 ` kargl at gcc dot gnu dot org
2007-02-04 12:03 ` pault at gcc dot gnu dot org
2007-02-04 22:57 ` milan at cmm dot ki dot si

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=20070204001331.28354.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).