public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Thomas dot Koenig at online dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/18518] equivalenced variables are not saved
Date: Thu, 18 Nov 2004 18:53:00 -0000	[thread overview]
Message-ID: <20041118185305.13692.qmail@sourceware.org> (raw)
In-Reply-To: <20041116103451.18518.Thomas.Koenig@online.de>


------- Additional Comments From Thomas dot Koenig at online dot de  2004-11-18 18:53 -------
It appears that equivalenced variables are not
saved.

Here's a simplified test case:

$ cat pr18518-test.f90
program main
  call foo
  call bar
  call foo
end program main

subroutine foo
  integer i,g,h
  data i/0/
  equivalence (g,h)
  save g
  if (i == 0) then
     i = 1
     h = 12345
  end if
  print *,h
end subroutine foo

subroutine bar
  integer a(10)
  a = 34
end subroutine bar
$ gfortran pr18518-test.f90 && ./a.out
       12345
          34

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|d1mach(4)  (BLAS) broken,   |equivalenced variables are
                   |g77 regression              |not saved


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


  parent reply	other threads:[~2004-11-18 18:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-16 10:35 [Bug fortran/18518] New: d1mach(4) (BLAS) broken, g77 regression Thomas dot Koenig at online dot de
2004-11-16 10:36 ` [Bug fortran/18518] " Thomas dot Koenig at online dot de
2004-11-16 13:59 ` pinskia at gcc dot gnu dot org
2004-11-17  8:46 ` c dot lemmen at fz-juelich dot de
2004-11-18  9:02 ` Thomas dot Koenig at online dot de
2004-11-18 18:53 ` Thomas dot Koenig at online dot de [this message]
2004-11-20 12:10 ` [Bug fortran/18518] equivalenced variables are not saved toon at moene dot indiv dot nluug dot nl
2004-11-20 13:20 ` Thomas dot Koenig at online dot de
2004-11-22 12:30 ` Thomas dot Koenig at online dot de
2004-11-30 15:18 ` tobi at gcc dot gnu dot org
2005-01-06 14:42 ` tobi at gcc dot gnu dot org
2005-03-01 14:11 ` pinskia at gcc dot gnu dot org
2005-03-10 14:34 ` pinskia at gcc dot gnu dot org
2005-09-27 21:47 ` cvs-commit at gcc dot gnu dot org
2005-09-29 21:30 ` cvs-commit at gcc dot gnu dot org
2005-09-29 21:33 ` pinskia 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=20041118185305.13692.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).