public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/57697] Segfault with defined assignment for components during intrinsic assignment
Date: Thu, 27 Jun 2013 09:23:00 -0000 [thread overview]
Message-ID: <bug-57697-4-iGEbkjEHT6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57697-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57697
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2013-06-27
Ever confirmed|0 |1
--- Comment #4 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
(In reply to Tobias Burnus from comment #3)
> > Should not this go to PR57696?
>
> No. The examples are similar, but they expose rather different bugs.
So confirmed.
next prev parent reply other threads:[~2013-06-27 9:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 11:23 [Bug fortran/57697] New: " burnus at gcc dot gnu.org
2013-06-24 13:16 ` [Bug fortran/57697] " burnus at gcc dot gnu.org
2013-06-24 13:22 ` dominiq at lps dot ens.fr
2013-06-24 13:30 ` burnus at gcc dot gnu.org
2013-06-27 9:23 ` dominiq at lps dot ens.fr [this message]
2013-08-21 12:35 ` [Bug fortran/57697] [OOP] " janus at gcc dot gnu.org
2013-09-10 6:13 ` burnus at gcc dot gnu.org
2013-09-15 10:54 ` burnus at gcc dot gnu.org
2013-09-16 6:42 ` burnus at gcc dot gnu.org
2013-09-18 22:19 ` burnus at gcc dot gnu.org
2013-09-19 6:44 ` burnus at gcc dot gnu.org
2013-09-19 8:42 ` dominiq at lps dot ens.fr
2013-09-19 17:12 ` burnus at gcc dot gnu.org
2013-09-19 18:05 ` dominiq at lps dot ens.fr
2013-09-21 13:19 ` dominiq at lps dot ens.fr
2013-09-25 19:54 ` burnus at gcc dot gnu.org
2013-10-04 16:26 ` burnus at gcc dot gnu.org
2013-10-04 16:55 ` burnus at gcc dot gnu.org
2013-10-04 16:56 ` burnus 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-57697-4-iGEbkjEHT6@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).