public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bangerth at dealii dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libf2c/15151] -m64 flag causes incorrect logical i/o (g77) Date: Fri, 30 Apr 2004 15:57:00 -0000 [thread overview] Message-ID: <20040430154522.13961.qmail@sources.redhat.com> (raw) In-Reply-To: <20040426153157.15151.eesrjhc@bath.ac.uk> ------- Additional Comments From bangerth at dealii dot org 2004-04-30 15:45 ------- Since 3.4.x is the last release branch on which g77 will be supported, it may make sense to fix it there even if it is not a regression. Let's let one of the g77 maintainers comment on this first, before we suspend this PR. W. -- What |Removed |Added ---------------------------------------------------------------------------- CC| |toon at moene dot indiv dot | |nluug dot nl Status|SUSPENDED |NEW Ever Confirmed| |1 Last reconfirmed|0000-00-00 00:00:00 |2004-04-30 15:45:21 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15151
next prev parent reply other threads:[~2004-04-30 15:45 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-04-26 16:55 [Bug fortran/15151] New: " eesrjhc at bath dot ac dot uk 2004-04-26 19:34 ` [Bug fortran/15151] " ebotcazou at gcc dot gnu dot org 2004-04-27 21:57 ` [Bug libf2c/15151] " pinskia at gcc dot gnu dot org 2004-04-27 22:11 ` pinskia at gcc dot gnu dot org 2004-04-28 1:40 ` bdavis9659 at comcast dot net 2004-04-30 15:51 ` [Bug fortran/15151] " eesrjhc at bath dot ac dot uk 2004-04-30 15:54 ` [Bug libf2c/15151] " pinskia at gcc dot gnu dot org 2004-04-30 15:57 ` bangerth at dealii dot org [this message] 2004-05-01 15:00 ` pinskia at gcc dot gnu dot org 2004-05-02 7:49 ` ebotcazou at gcc dot gnu dot org 2004-05-06 11:33 ` [Bug libf2c/15151] incorrect logical i/o in 64-bit mode bdavis9659 at comcast dot net 2004-06-14 17:25 ` [Bug libf2c/15151] [g77] " mmitchel at gcc dot gnu dot org 2004-06-19 11:12 ` toon at moene dot indiv dot nluug dot nl 2004-06-19 15: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=20040430154522.13961.qmail@sources.redhat.com \ --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).