public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/59612] iso_fortran_env segfaults with -fdump-fortran-original
Date: Sat, 28 Dec 2013 15:53:00 -0000	[thread overview]
Message-ID: <bug-59612-4-7RmMWTuOBu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59612-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59612

--- Comment #4 from janus at gcc dot gnu.org ---
(In reply to janus from comment #3)
> Maybe it would make sense to run the testsuite with -fdump-fortran-original,
> in order to check for further problems:

Does not seem to yield any failures here (with the patch from comment 1
applied).


  parent reply	other threads:[~2013-12-28 15:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-27 21:40 [Bug fortran/59612] New: " tkoenig at gcc dot gnu.org
2013-12-28 13:40 ` [Bug fortran/59612] " janus at gcc dot gnu.org
2013-12-28 14:33 ` janus at gcc dot gnu.org
2013-12-28 15:53 ` janus at gcc dot gnu.org [this message]
2013-12-29 17:20 ` janus at gcc dot gnu.org
2013-12-29 18:08 ` janus at gcc dot gnu.org
2014-01-11 20:35 ` [Bug fortran/59612] [F03] " janus at gcc dot gnu.org
2014-01-11 22:48 ` janus at gcc dot gnu.org
2014-02-08 13:22 ` dominiq at lps dot ens.fr
2014-05-24 19:08 ` dominiq at lps dot ens.fr

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-59612-4-7RmMWTuOBu@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).