public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sgk at troutmask dot apl dot washington dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/38724] Segfault caused by derived-type with allocatable component in private clause
Date: Mon, 05 Jan 2009 02:32:00 -0000 [thread overview]
Message-ID: <20090105023222.28911.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38724-10110@http.gcc.gnu.org/bugzilla/>
------- Comment #6 from sgk at troutmask dot apl dot washington dot edu 2009-01-05 02:32 -------
Subject: Re: Segfault caused by derived-type with allocatable component in
private clause
On Sun, Jan 04, 2009 at 09:31:20PM -0000, jakub at gcc dot gnu dot org wrote:
>
> ------- Comment #5 from jakub at gcc dot gnu dot org 2009-01-04 21:31 -------
> OpenMP 3.0 doesn't cover types with allocatable components, so this is
> undefined. If anything IMHO we should reject any attempts to privatize
> types with allocatable components, because it isn't clear what will OpenMP 4.0
> require for them and if we now implement something different, it might be a
> compatibility problem.
>
OK. Thanks for the info concerning OpenMP 3.0 and allocatable components.
I agree gfortran should reject the program until we have some idea of
the behavior with regards to OpenMP 4.0.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38724
next prev parent reply other threads:[~2009-01-05 2:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-04 19:41 [Bug libgomp/38724] New: Segfault " kargl at gcc dot gnu dot org
2009-01-04 19:42 ` [Bug libgomp/38724] " kargl at gcc dot gnu dot org
2009-01-04 19:43 ` kargl at gcc dot gnu dot org
2009-01-04 19:46 ` kargl at gcc dot gnu dot org
2009-01-04 19:47 ` [Bug libgomp/38724] Segfault caused by derived-type " kargl at gcc dot gnu dot org
2009-01-04 21:31 ` jakub at gcc dot gnu dot org
2009-01-05 2:32 ` sgk at troutmask dot apl dot washington dot edu [this message]
[not found] <bug-38724-4@http.gcc.gnu.org/bugzilla/>
2013-08-12 12:46 ` 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=20090105023222.28911.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).