public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/26064] 4.1 regression introduced with patch for bug 18197 Date: Wed, 01 Feb 2006 14:46:00 -0000 [thread overview] Message-ID: <20060201144559.6926.qmail@sourceware.org> (raw) In-Reply-To: <bug-26064-11543@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from pinskia at gcc dot gnu dot org 2006-02-01 14:45 ------- This looks related to PR 26041. Can you try the patch at http://gcc.gnu.org/ml/gcc-patches/2006-01/msg02261.html ? -- pinskia at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- BugsThisDependsOn| |26041 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26064
next prev parent reply other threads:[~2006-02-01 14:46 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-02-01 14:27 [Bug fortran/26064] New: " sven dot buijssen at math dot uni-dortmund dot de 2006-02-01 14:46 ` pinskia at gcc dot gnu dot org [this message] 2006-02-01 16:36 ` [Bug fortran/26064] " sven dot buijssen at math dot uni-dortmund dot de 2006-02-01 16:49 ` hjl at lucon dot org 2006-02-01 17:00 ` hjl at lucon dot org 2006-02-01 20:01 ` sven dot buijssen at math dot uni-dortmund dot de 2006-02-01 21:20 ` hjl at lucon dot org 2006-02-02 1:19 ` hjl at lucon dot org 2006-02-02 11:30 ` sven dot buijssen at math dot uni-dortmund dot de 2006-02-02 14:49 ` hjl at lucon dot org 2006-02-02 16:12 ` sven dot buijssen at math dot uni-dortmund dot de 2006-02-05 19:52 ` hjl at gcc dot gnu dot org 2006-02-05 19:53 ` hjl at gcc dot gnu dot org 2006-03-07 22:29 ` hjl at gcc dot gnu dot org 2006-03-07 22:31 ` hjl 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=20060201144559.6926.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).