public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/46196] [OOP] gfortran compiles invalid generic TBP: dummy arguments are type compatible Date: Wed, 27 Oct 2010 21:51:00 -0000 [thread overview] Message-ID: <20101027215100.Pw2QXExalWMBZccDr23OpzbY8tMOYanmicZD-F0VeP4@z> (raw) In-Reply-To: <bug-46196-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46196 --- Comment #3 from Dominique d'Humieres <dominiq at lps dot ens.fr> 2010-10-27 21:51:23 UTC --- With the patch in comment #2, several of my codelets are rejected: for instance the test in comment #24 of pr42274 is rejected with: [macbook] f90/bug% gfc pr42274_5.f90 pr42274_5.f90:14.33: generic, public :: extract => make_integer_2 1 Error: 'make_integer_2' and 'make_integer' for GENERIC 'extract' at (1) are ambiguous pr42274_5.f90:33.7: use m 1 Fatal Error: Can't open module file 'm.mod' for reading at (1): No such file or directory If you need I can sort out the other similar new errors tomorrow.
next prev parent reply other threads:[~2010-10-27 21:51 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-10-27 9:34 [Bug fortran/46196] New: " boschmann at tp1 dot physik.uni-siegen.de 2010-10-27 11:58 ` [Bug fortran/46196] " janus at gcc dot gnu.org 2010-10-27 20:32 ` janus at gcc dot gnu.org 2010-10-27 21:51 ` dominiq at lps dot ens.fr [this message] 2010-10-28 15:33 ` janus at gcc dot gnu.org 2010-10-28 21:06 ` dominiq at lps dot ens.fr 2010-10-28 21:58 ` mikael at gcc dot gnu.org 2010-10-29 8:31 ` janus at gcc dot gnu.org 2010-10-29 16:01 ` dominiq at lps dot ens.fr 2010-10-30 9:33 ` janus at gcc dot gnu.org 2010-10-30 11:52 ` dominiq at lps dot ens.fr 2010-10-30 12:52 ` mikael at gcc dot gnu.org 2010-10-30 13:53 ` janus at gcc dot gnu.org 2010-10-30 14:31 ` janus at gcc dot gnu.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=20101027215100.Pw2QXExalWMBZccDr23OpzbY8tMOYanmicZD-F0VeP4@z \ --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: linkBe 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).