From: "Dominique d'Humières" <dominiq@lps.ens.fr>
To: Andre Vehreschild <vehre@gmx.de>
Cc: Mikael Morin <mikael.morin@sfr.fr>,
Paul Richard Thomas <paul.richard.thomas@gmail.com>,
GNU GFortran <fortran@gcc.gnu.org>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch, Fortran, 66927, v2] [6 Regression] ICE in gfc_conf_procedure_call
Date: Wed, 07 Oct 2015 17:51:00 -0000 [thread overview]
Message-ID: <C293A715-AE4B-4D83-81DB-B529D65621B1@lps.ens.fr> (raw)
This patch also fixes pr57117 comment 2, the original test and the test in comment 3 now give an ICE
pr57117.f90:82:0:
allocate(z(9), source=reshape(x, (/ 9 /)))
1
internal compiler error: Segmentation fault: 11
and pr67044.
Thanks,
Dominique
next reply other threads:[~2015-10-07 17:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 17:51 Dominique d'Humières [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-10-25 11:51 Paul Richard Thomas
2015-10-25 13:09 ` Andre Vehreschild
2015-08-06 10:53 [Patch, Fortran, 66927, v1] " Andre Vehreschild
2015-08-06 12:01 ` Mikael Morin
2015-08-09 12:37 ` Mikael Morin
2015-09-29 14:27 ` [Patch, Fortran, 66927, v2] " Andre Vehreschild
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=C293A715-AE4B-4D83-81DB-B529D65621B1@lps.ens.fr \
--to=dominiq@lps.ens.fr \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=mikael.morin@sfr.fr \
--cc=paul.richard.thomas@gmail.com \
--cc=vehre@gmx.de \
/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).