public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/55282] [OOP] openmp directive and classes
Date: Mon, 12 Nov 2012 20:02:00 -0000	[thread overview]
Message-ID: <bug-55282-4-w4v4fKwDrp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55282-4@http.gcc.gnu.org/bugzilla/>


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

kargl at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kargl at gcc dot gnu.org

--- Comment #4 from kargl at gcc dot gnu.org 2012-11-12 20:02:02 UTC ---
(In reply to comment #3)
> Thanks pointing that. Is there any reason for not allowing the classes in
> openmp?
> I noticed that other compilers (eg ifort, xlf) can accommodate with this
> deviation from the standard, is gfortran going in the same direction?

Of course there is a good reason.  What if a future OpenMP
standard introduces classes in manner that conflicts with
the way gfortran implements the extension?  gfortran would
then need an option to toggle between the standard conforming
code and the GNU Fortran extension.  Which, then, is the
default?


  parent reply	other threads:[~2012-11-12 20:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-12 10:20 [Bug fortran/55282] New: " valeryweber at hotmail dot com
2012-11-12 14:36 ` [Bug fortran/55282] [OOP] " janus at gcc dot gnu.org
2012-11-12 14:47 ` janus at gcc dot gnu.org
2012-11-12 19:18 ` valeryweber at hotmail dot com
2012-11-12 20:02 ` kargl at gcc dot gnu.org [this message]
2012-11-13 10:44 ` burnus at gcc dot gnu.org
2012-11-13 16:57 ` valeryweber at hotmail dot com
2013-03-17 17:07 ` 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=bug-55282-4-w4v4fKwDrp@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).