public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/103039] [12 Regression] Segfault with openmp block within a select type block since r12-1016-g0e3b3b77e13cac76
Date: Wed, 09 Mar 2022 14:27:49 +0000 [thread overview]
Message-ID: <bug-103039-4-fQMbsaaBs7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103039-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103039
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2022-03-09
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
Keywords| |wrong-code
Priority|P3 |P1
--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
in .ompexp I see
void MAIN__._omp_fn.0 (struct .omp_data_s.9 & restrict .omp_data_i)
{
...
<bb 6> :
s = 0;
D.4352 = .omp_data_i->__tmp_class_a;
__tmp_class_a.10 = __tmp_class_a;
D.4355 = D.4352->_vptr;
__tmp_class_a.10->_vptr = D.4355;
D.4356 = .omp_data_i->__tmp_class_a;
D.4357 = D.4356->_vptr;
D.4358 = D.4357->_size;
D.4359 = (unsigned long) D.4358;
__tmp_class_a.11 = __tmp_class_a;
D.4361 = __builtin_malloc (D.4359);
__tmp_class_a.11->_data = D.4361;
D.4362 = .omp_data_i->__tmp_class_a;
D.4363 = D.4362->_vptr;
D.4364 = D.4363->_copy;
__tmp_class_a.12 = __tmp_class_a;
D.4366 = .omp_data_i->__tmp_class_a;
D.4367 = D.4366->_data;
D.4364 (D.4367, __tmp_class_a.12);
so .omp_data_i->__tmp_class_a is accessed but then the local __tmp_class_a
is used in the end. So sth is amiss here.
I suspect the unshare_expr is playing havoc with some later lookups.
next prev parent reply other threads:[~2022-03-09 14:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 9:08 [Bug fortran/103039] New: Segfault with openmp block within a select type block mscfd at gmx dot net
2021-11-02 9:12 ` [Bug fortran/103039] " mscfd at gmx dot net
2021-11-02 9:20 ` marxin at gcc dot gnu.org
2021-11-02 10:26 ` [Bug fortran/103039] Segfault with openmp block within a select type block since r12-1016-g0e3b3b77e13cac76 mscfd at gmx dot net
2022-01-25 8:28 ` mscfd at gmx dot net
2022-01-25 9:16 ` [Bug fortran/103039] [12 Regression] " jakub at gcc dot gnu.org
2022-03-09 14:27 ` rguenth at gcc dot gnu.org [this message]
2022-03-17 16:41 ` jakub at gcc dot gnu.org
2022-03-18 12:29 ` burnus at gcc dot gnu.org
2022-03-18 12:37 ` jakub at gcc dot gnu.org
2022-03-18 13:50 ` cvs-commit at gcc dot gnu.org
2022-03-18 16:40 ` cvs-commit at gcc dot gnu.org
2022-03-18 16:42 ` burnus at gcc dot gnu.org
2022-03-21 11:59 ` mscfd at gmx dot net
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-103039-4-fQMbsaaBs7@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).