From: Paul Richard Thomas <paul.richard.thomas@gmail.com>
To: Thomas Koenig <tkoenig@netcologne.de>
Cc: fortran@gcc.gnu.org, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch, fortran] PR48462 - [4.6/4.7 Regression] realloc on assignment: matmul Segmentation Fault with Allocatable Array + PR48746
Date: Sat, 30 Apr 2011 10:50:00 -0000 [thread overview]
Message-ID: <BANLkTi=7dhX4hqCcVZX80FHfwPdt8ZEccA@mail.gmail.com> (raw)
In-Reply-To: <4DBB185C.1050408@netcologne.de>
Dear Thomas,
> there's another point: The sizes are also not set correctly.
Oh dear, oh dear! I am losing it in my old age. :-(
Thanks
Paul
next prev parent reply other threads:[~2011-04-30 7:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-29 17:49 Paul Richard Thomas
2011-04-29 17:53 ` Steve Kargl
2011-04-29 20:45 ` Thomas Koenig
2011-04-29 21:08 ` Thomas Koenig
2011-04-30 10:50 ` Paul Richard Thomas [this message]
2011-04-30 14:05 ` Paul Richard Thomas
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='BANLkTi=7dhX4hqCcVZX80FHfwPdt8ZEccA@mail.gmail.com' \
--to=paul.richard.thomas@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=tkoenig@netcologne.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).