This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/55282] [OOP] openmp directive and classes
- From: "kargl at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 12 Nov 2012 20:02:02 +0000
- Subject: [Bug fortran/55282] [OOP] openmp directive and classes
- Auto-submitted: auto-generated
- References: <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?