public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/103790] internal compiler error: Segmentation fault when playing with coroutine Date: Fri, 28 Jan 2022 11:36:20 +0000 [thread overview] Message-ID: <bug-103790-4-Ofe9eduKFs@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103790-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103790 --- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Andre Vehreschild <vehre@gcc.gnu.org>: https://gcc.gnu.org/g:26e237fb5b83582b30ef7c5a388bc4e968a5a289 commit r12-6915-g26e237fb5b83582b30ef7c5a388bc4e968a5a289 Author: Andre Vehreschild <vehre@gcc.gnu.org> Date: Fri Jan 28 12:34:17 2022 +0100 Prevent malicious descriptor stacking for scalar components [V2]. gcc/fortran/ChangeLog: PR fortran/103790 * trans-array.cc (structure_alloc_comps): Prevent descriptor stacking for non-array data; do not broadcast caf-tokens. * trans-intrinsic.cc (conv_co_collective): Prevent generation of unused descriptor. gcc/testsuite/ChangeLog: PR fortran/103790 * gfortran.dg/coarray_collectives_18.f90: New test.
next prev parent reply other threads:[~2022-01-28 11:36 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-21 14:14 [Bug c++/103790] New: " jack.cui2 at foxmail dot com 2021-12-21 14:39 ` [Bug c++/103790] " marxin at gcc dot gnu.org 2021-12-21 14:47 ` iains at gcc dot gnu.org 2021-12-21 14:52 ` marxin at gcc dot gnu.org 2021-12-21 14:54 ` iains at gcc dot gnu.org 2021-12-21 19:38 ` pinskia at gcc dot gnu.org 2022-01-28 9:05 ` cvs-commit at gcc dot gnu.org 2022-01-28 11:36 ` cvs-commit at gcc dot gnu.org [this message] 2022-02-14 15:18 ` cvs-commit 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-103790-4-Ofe9eduKFs@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: linkBe 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).