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/38724] Segfault caused by derived-type with allocatable component in private clause
Date: Mon, 12 Aug 2013 13:05:00 -0000	[thread overview]
Message-ID: <bug-38724-4-ITQesognjW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-38724-4@http.gcc.gnu.org/bugzilla/>

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

janus at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |accepts-invalid
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2013-08-12
          Component|libgomp                     |fortran
     Ever confirmed|0                           |1

--- Comment #8 from janus at gcc dot gnu.org ---
(In reply to Steve Kargl from comment #6)
> I agree gfortran should reject the program until we have some idea of
> the behavior with regards to OpenMP 4.0.

It seems that the final OpenMP 4.0 specification does not support allocatable
components. In particular it lists "Allocatable enhancement" as unsupported,
which supposedly refers to TR 15581 and therefore includes alloc. comp., see

http://openmp.org/wp/openmp-specifications/

So the test case should probably be rejected by the front end (alternatively:
support it as a GNU extension).


  parent reply	other threads:[~2013-08-12 13:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-38724-4@http.gcc.gnu.org/bugzilla/>
2013-08-12 12:46 ` [Bug libgomp/38724] " janus at gcc dot gnu.org
2013-08-12 13:05 ` janus at gcc dot gnu.org [this message]
2015-01-03 10:27 ` [Bug fortran/38724] Segfault caused by derived-type with allocatable component in OpenMP " 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-38724-4-ITQesognjW@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).