public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/97589] Segementation fault when allocating coarrays.
Date: Sun, 22 Nov 2020 13:20:39 +0000 [thread overview]
Message-ID: <bug-97589-4-dg7leWEpgY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97589-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97589
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
--- Comment #18 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Hi Toon,
with https://gcc.gnu.org/pipermail/gcc-cvs/2020-November/337586.html ,
your program seems to work (at least the values look reasonable):
Decomposition information on image 2 : there are 3 * 2 slabs; the slabs
are 24 * 35 grid cells in size.
Decomposition information on image 5 : there are 3 * 2 slabs; the slabs
are 24 * 35 grid cells in size.
Decomposition information on image 3 : there are 3 * 2 slabs; the slabs
are 24 * 35 grid cells in size.
Decomposition information on image 1 : there are 3 * 2 slabs; the slabs
are 24 * 35 grid cells in size.
Decomposition information on image 4 : there are 3 * 2 slabs; the slabs
are 24 * 35 grid cells in size.
Decomposition information on image 6 : there are 3 * 2 slabs; the slabs
are 24 * 35 grid cells in size.
Time 0 Image 5 PS= 99978.4531 T= 300.364166
U= 19.3067131 V= 15.9685030 W= 0.138491884 Q=
2.17480748E-03
Time 0 Image 1 PS= 99985.0938 T= 300.027161
U= -9.06420994 V= 5.92245483 W= 0.137841657 Q=
2.10389541E-03
Time 0 Image 3 PS= 99999.3828 T= 300.014618
U= -4.48150349 V= -1.37469864 W= -8.73371959E-02 Q=
1.81287562E-03
Time 0 Image 2 PS= 99986.4141 T= 300.200836
U= -3.47342205 V= 16.5930214 W= 0.205771178 Q=
1.97321200E-03
Time 0 Image 6 PS= 99980.4141 T= 300.424133
U= 12.8092175 V= 11.5236654 W= 6.01452552E-02 Q=
1.87643641E-03
Time 0 Image 4 PS= 100010.516 T= 300.005005
U= 11.4250631 V= 3.44926071 W= -0.227272436 Q=
2.07653991E-03
Time 240 Image 6 PS= 99990.5781 T= 300.666931
U= 22.8395500 V= -11.9721365 W= 3.66642363E-02 Q=
1.70292379E-03
Time 240 Image 2 PS= 99980.1484 T= 300.538757
U= 19.1216316 V= 34.7150421 W= 3.16514075E-03 Q=
2.09417334E-03
Time 240 Image 1 PS= 99969.6641 T= 300.400970
U= 3.65581894 V= 16.8670387 W= 2.10290849E-02 Q=
2.06003617E-03
Time 240 Image 3 PS= 99995.2734 T= 300.354370
U= 4.84142876 V= 4.59838200 W= 1.12933442E-02 Q=
1.67453510E-03
Time 240 Image 5 PS= 99959.9141 T= 300.308228
U= 35.2094879 V= 26.3194275 W= 6.13999888E-02 Q=
2.24495190E-03
Time 240 Image 4 PS= 100024.211 T= 300.642700
U= -21.4838848 V= -5.71874714 W= 0.123860441 Q=
1.77718676E-03
Time 480 Image 1 PS= 99988.9688 T= 300.262726
U= -1.55552006 V= 13.3446560 W= -1.83758438E-02 Q=
1.98666588E-03
Time 480 Image 5 PS= 100030.500 T= 300.034546
U= 8.11599827 V= 49.5809326 W= -1.16332620E-02 Q=
2.18066899E-03
Time 480 Image 3 PS= 99974.3828 T= 300.171265
U= -12.1284695 V= 13.2599001 W= -0.132261544 Q=
1.64680334E-03
Time 480 Image 6 PS= 99983.6328 T= 299.253204
U= -16.0964108 V= -7.74500656 W= -0.392248750 Q=
1.88040221E-03
Time 480 Image 2 PS= 99969.3672 T= 299.095215
U= -5.18578625 V= 36.8412170 W= -0.231359661 Q=
1.97951938E-03
Time 480 Image 4 PS= 100016.453 T= 300.540619
U= -1.72649384 V= 38.7740860 W= -0.185899958 Q=
2.31738412E-03
Thanks again for the test case, it certainly showed up a lot of bugs :-)
next prev parent reply other threads:[~2020-11-22 13:20 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 11:58 [Bug fortran/97589] New: " toon at moene dot org
2020-10-29 21:17 ` [Bug fortran/97589] " tkoenig at gcc dot gnu.org
2020-10-29 21:24 ` tkoenig at gcc dot gnu.org
2020-11-08 12:00 ` tkoenig at gcc dot gnu.org
2020-11-09 20:39 ` tkoenig at gcc dot gnu.org
2020-11-09 20:48 ` tkoenig at gcc dot gnu.org
2020-11-09 21:43 ` tkoenig at gcc dot gnu.org
2020-11-10 8:03 ` toon at moene dot org
2020-11-10 9:02 ` tkoenig at gcc dot gnu.org
2020-11-14 14:53 ` toon at moene dot org
2020-11-15 11:43 ` tkoenig at gcc dot gnu.org
2020-11-15 18:30 ` toon at moene dot org
2020-11-16 18:50 ` tkoenig at gcc dot gnu.org
2020-11-16 20:27 ` tkoenig at gcc dot gnu.org
2020-11-16 20:33 ` tkoenig at gcc dot gnu.org
2020-11-16 21:15 ` tkoenig at gcc dot gnu.org
2020-11-16 21:15 ` tkoenig at gcc dot gnu.org
2020-11-17 13:18 ` tkoenig at gcc dot gnu.org
2020-11-22 13:20 ` tkoenig at gcc dot gnu.org [this message]
2020-11-22 18:10 ` toon at moene dot org
2020-11-22 19:10 ` toon at moene dot org
2020-11-22 20:27 ` tkoenig at gcc dot gnu.org
2020-11-26 22:41 ` tkoenig at gcc dot gnu.org
2020-11-27 8:34 ` toon at moene dot org
2020-11-27 14:35 ` toon at moene dot org
2020-11-27 17:52 ` toon at moene dot org
2020-11-28 17:16 ` tkoenig at gcc dot gnu.org
2020-11-28 20:12 ` toon at moene dot org
2021-09-08 20:05 ` anlauf at gcc dot gnu.org
2021-09-09 7:01 ` toon at moene dot org
2021-09-09 18:08 ` anlauf 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-97589-4-dg7leWEpgY@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).