public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pault at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/35476] Accepts invalid: USE/host association of generics with same specifics
Date: Sat, 15 Mar 2008 22:41:00 -0000	[thread overview]
Message-ID: <20080315224043.783.qmail@sourceware.org> (raw)
In-Reply-To: <bug-35476-13404@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from pault at gcc dot gnu dot org  2008-03-15 22:40 -------
(In reply to comment #3)
> (In reply to comment #0)
> > - openf95 and sunf95 reject it
> > - ifort, gfortran, NAG f95, and g95 accept it
> > Bill Long writes that he tested two non-Sun compilers, of which two gave an
> > error and two did not.
> 
> For what it's worth, the IBM compiler also accepts it. (Now, which is the
> second non-Sun compiler that rejects it?)
> 

Where are we at with the J3 discussion?  I rather think that it is a bug....

Paul


-- 


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


  parent reply	other threads:[~2008-03-15 22:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-05 17:46 [Bug fortran/35476] New: " burnus at gcc dot gnu dot org
2008-03-05 22:06 ` [Bug fortran/35476] " pault at gcc dot gnu dot org
2008-03-06  7:01 ` burnus at gcc dot gnu dot org
2008-03-07 12:04 ` fxcoudert at gcc dot gnu dot org
2008-03-15 22:41 ` pault at gcc dot gnu dot org [this message]
2008-04-12 10:34 ` burnus at gcc dot gnu dot org
2009-02-11 15:11 ` pault at gcc dot gnu dot org
2009-02-11 15:36 ` burnus at gcc dot gnu dot org
2009-12-17 22:50 ` burnus at gcc dot gnu dot org
     [not found] <bug-35476-4@http.gcc.gnu.org/bugzilla/>
2012-01-28 22:33 ` dominiq at lps dot ens.fr
2012-01-28 23:09 ` burnus 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=20080315224043.783.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).