public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "anlauf at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/59093] Segfault in gfc_trans_pointer_assignment
Date: Sun, 25 Jan 2015 21:30:00 -0000 [thread overview]
Message-ID: <bug-59093-4-Vq7YGANCDK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59093-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59093
Harald Anlauf <anlauf at gmx dot de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |anlauf at gmx dot de
--- Comment #8 from Harald Anlauf <anlauf at gmx dot de> ---
(In reply to Matt Thompson from comment #7)
> I'm not sure if anyone is even looking at this bug anymore, but I wanted to
> say it is still present in gcc 4.9.1. Using the test from janus@gcc.gnu.org:
Still present in gcc 5 trunk rev. 220062.
next prev parent reply other threads:[~2015-01-25 21:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 20:16 [Bug fortran/59093] New: internal compiler error: Segmentation fault compiling F90 File matthew.thompson at nasa dot gov
2013-11-12 20:58 ` [Bug fortran/59093] " dominiq at lps dot ens.fr
2013-11-12 21:13 ` dominiq at lps dot ens.fr
2014-01-04 17:17 ` janus at gcc dot gnu.org
2014-03-19 19:04 ` [Bug fortran/59093] Segfault in gfc_trans_pointer_assignment matthew.thompson at nasa dot gov
2014-03-26 18:29 ` matthew.thompson at nasa dot gov
2014-06-11 11:50 ` matthew.thompson at nasa dot gov
2015-01-25 21:30 ` anlauf at gmx dot de [this message]
2015-05-21 16:12 ` matthew.thompson at nasa dot gov
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-59093-4-Vq7YGANCDK@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).