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] [F03] iso_fortran_env segfaults with -fdump-fortran-original Date: Sat, 11 Jan 2014 20:35:00 -0000 [thread overview] Message-ID: <bug-59612-4-ZsmBgDxipQ@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 #8 from janus at gcc dot gnu.org --- Author: janus Date: Sat Jan 11 20:34:48 2014 New Revision: 206556 URL: http://gcc.gnu.org/viewcvs?rev=206556&root=gcc&view=rev Log: 2014-01-11 Janus Weil <janus@gcc.gnu.org> Backport from mainline 2013-12-29 Janus Weil <janus@gcc.gnu.org> PR fortran/59612 PR fortran/57042 * dump-parse-tree.c (show_typespec): Check for charlen. * invoke.texi: Fix documentation of -fdump-fortran-optimized and -fdump-parse-tree. Modified: branches/gcc-4_8-branch/gcc/fortran/ChangeLog branches/gcc-4_8-branch/gcc/fortran/dump-parse-tree.c branches/gcc-4_8-branch/gcc/fortran/invoke.texi
next prev parent reply other threads:[~2014-01-11 20:35 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 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 ` janus at gcc dot gnu.org [this message] 2014-01-11 22:48 ` [Bug fortran/59612] [F03] " 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-ZsmBgDxipQ@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: linkBe 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).