public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/53718] [4.7/4.8 regression] [OOP] gfortran generates asm label twice in the same output file
Date: Mon, 18 Jun 2012 20:04:00 -0000	[thread overview]
Message-ID: <bug-53718-4-38bjtX3rct@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53718-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from janus at gcc dot gnu.org 2012-06-18 20:04:09 UTC ---
(In reply to comment #2)
> just as a side note: most of my bugreports come from compiling babel's
> regression test suite. Babel is a language interoperability tool that (also)
> generates bindings for Fortran 2003. It's free (LGPL) and it might be a very
> good testcase for gfortran in the future.
> 
> https://computation.llnl.gov/casc/components/

Thanks for the pointer. Sounds interesting.


Btw, here is a slightly different (but much simpler) test case, which exhibits
the same problem:


module m
  type t
  end type
end module

subroutine sub1
  use m
  class(t), pointer :: a1
end subroutine

subroutine sub2
  use m
  class(t), pointer :: a2
end subroutine


This structure is rather unusual for F03 object-oriented code, since it
involves 'naked' subroutines (F77 style), which are not part of any MODULE or
PROGRAM. Putting both routines into a module or program makes the error go
away.


  parent reply	other threads:[~2012-06-18 20:04 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-18 17:43 [Bug fortran/53718] New: " adrian at llnl dot gov
2012-06-18 18:46 ` [Bug fortran/53718] [4.7/4.8 regression] [OOP] " janus at gcc dot gnu.org
2012-06-18 18:55 ` adrian at llnl dot gov
2012-06-18 20:04 ` janus at gcc dot gnu.org [this message]
2012-06-18 20:36 ` dominiq at lps dot ens.fr
2012-06-18 20:45 ` dominiq at lps dot ens.fr
2012-06-19  9:15 ` rguenth at gcc dot gnu.org
2012-06-19 10:35 ` janus at gcc dot gnu.org
2012-06-19 13:13 ` janus at gcc dot gnu.org
2012-06-19 17:36 ` dominiq at lps dot ens.fr
2012-06-20  9:19 ` janus at gcc dot gnu.org
2012-09-07  8:13 ` rguenth at gcc dot gnu.org
2012-09-11 13:48 ` burnus at gcc dot gnu.org
2012-09-11 15:57 ` janus at gcc dot gnu.org
2012-09-20 10:28 ` jakub at gcc dot gnu.org
2012-10-31 21:56 ` janus at gcc dot gnu.org
2012-10-31 22:03 ` [Bug fortran/53718] [4.7 " janus at gcc dot gnu.org
2013-01-27 21:32 ` janus at gcc dot gnu.org
2013-04-11  8:00 ` rguenth at gcc dot gnu.org
2014-06-12 13:12 ` rguenth at gcc dot gnu.org
2014-06-12 13:33 ` dominiq at lps dot ens.fr

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=bug-53718-4-38bjtX3rct@http.gcc.gnu.org/bugzilla/ \
    --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).