public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kargl at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/25041] gfortran internal compiler error: Segmentation fault when compiling 'rksuite_90' Date: Sat, 26 Nov 2005 02:49:00 -0000 [thread overview] Message-ID: <20051126024953.7729.qmail@sourceware.org> (raw) In-Reply-To: <bug-25041-11768@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from kargl at gcc dot gnu dot org 2005-11-26 02:49 ------- Reduce test case. module z type b character(len=80) :: r(10) end type b contains subroutine a(c) type(b), intent(inout), target :: c write (c%r,"(a)") "death" end subroutine a end module z -- kargl at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last reconfirmed|0000-00-00 00:00:00 |2005-11-26 02:49:53 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25041
next prev parent reply other threads:[~2005-11-26 2:49 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-11-26 0:00 [Bug fortran/25041] New: " haymaker at mail dot utexas dot edu 2005-11-26 0:11 ` [Bug fortran/25041] " kargl at gcc dot gnu dot org 2005-11-26 2:49 ` kargl at gcc dot gnu dot org [this message] 2005-11-26 6:03 ` haymaker at mail dot utexas dot edu 2006-01-01 6:53 ` pinskia at gcc dot gnu dot 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=20051126024953.7729.qmail@sourceware.org \ --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).