public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pault at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/26106] [meta-bug] Gfortran can't compile tonto Date: Wed, 19 Apr 2006 04:59:00 -0000 [thread overview] Message-ID: <20060419045956.14519.qmail@sourceware.org> (raw) In-Reply-To: <bug-26106-682@http.gcc.gnu.org/bugzilla/> ------- Comment #18 from pault at gcc dot gnu dot org 2006-04-19 04:59 ------- (In reply to comment #15) > I can now compile tonto-1.0 without any kludges or tricks. That said, it > segfaults immediately after reading the input data. I will endeavour to find > the cause. This happens in a call to intrinsic flush, during the initial input. > > tonto-2.x is blocked by complex(ie. complicated) constructors, which in the > words of "Hitch-hikers Guide to the Galaxy", "will take a little while"; > although I hope to improve on the 4 million years of the story.... > > Paul > Please see yesterday's submission of a patch for this: http://gcc.gnu.org/ml/fortran/2006-04/msg00221.html Paul -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26106
next prev parent reply other threads:[~2006-04-19 4:59 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-02-05 16:39 [Bug fortran/26106] New: " hjl at lucon dot org 2006-02-05 16:41 ` [Bug fortran/26106] [meta-bug] " pinskia at gcc dot gnu dot org 2006-02-05 17:37 ` pinskia at gcc dot gnu dot org 2006-03-11 19:27 ` kargl at gcc dot gnu dot org 2006-03-11 20:15 ` hjl at lucon dot org 2006-03-15 16:53 ` pault at gcc dot gnu dot org 2006-03-15 17:26 ` kargl at gcc dot gnu dot org 2006-03-15 19:31 ` hjl at lucon dot org 2006-03-15 20:02 ` kargl at gcc dot gnu dot org 2006-03-15 20:18 ` hjl at lucon dot org 2006-03-15 20:42 ` kargl at gcc dot gnu dot org 2006-03-15 23:28 ` hjl at lucon dot org 2006-03-15 23:33 ` Andrew Pinski 2006-03-15 23:33 ` pinskia at physics dot uc dot edu 2006-03-16 0:14 ` hjl at lucon dot org 2006-03-16 5:08 ` pinskia at gcc dot gnu dot org 2006-04-10 15:07 ` paul dot richard dot thomas at cea dot fr 2006-04-13 13:36 ` paul dot richard dot thomas at cea dot fr 2006-04-13 13:48 ` hjl at lucon dot org 2006-04-13 13:49 ` hjl at lucon dot org 2006-04-19 4:59 ` pault at gcc dot gnu dot org [this message] 2006-04-20 6:21 ` jvdelisle at gcc dot gnu dot org 2006-04-20 6:25 ` jvdelisle at gcc dot gnu dot org 2006-04-22 4:48 ` jvdelisle at gcc dot gnu dot org 2006-05-30 16:09 ` [Bug fortran/26106] [meta-bug] Gfortran can't compile tonto correctly hjl at lucon dot org 2006-07-30 23:27 ` hjl at lucon dot org 2006-08-10 12:11 ` paul dot richard dot thomas at cea dot fr 2006-08-10 16:40 ` hjl at lucon 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=20060419045956.14519.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).