public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/32760] Error defining subroutine named PRINT Date: Thu, 26 Jul 2007 04:56:00 -0000 [thread overview] Message-ID: <20070726045619.28479.qmail@sourceware.org> (raw) In-Reply-To: <bug-32760-6318@http.gcc.gnu.org/bugzilla/> ------- Comment #13 from jvdelisle at gcc dot gnu dot org 2007-07-26 04:56 ------- I will prepare a submittal to the list. Regression tested OK too. -- jvdelisle at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|unassigned at gcc dot gnu |jvdelisle at gcc dot gnu dot |dot org |org Status|NEW |ASSIGNED Last reconfirmed|2007-07-22 17:39:16 |2007-07-26 04:56:18 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32760
next prev parent reply other threads:[~2007-07-26 4:56 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-07-13 22:38 [Bug fortran/32760] New: [4.3 regression] " anlauf at gmx dot de 2007-07-13 23:45 ` [Bug fortran/32760] " dfranke at gcc dot gnu dot org 2007-07-14 10:21 ` anlauf at gmx dot de 2007-07-16 9:58 ` [Bug fortran/32760] " burnus at gcc dot gnu dot org 2007-07-17 4:26 ` jvdelisle at gcc dot gnu dot org 2007-07-22 4:08 ` jvdelisle at gcc dot gnu dot org 2007-07-22 8:21 ` dfranke at gcc dot gnu dot org 2007-07-22 17:39 ` dfranke at gcc dot gnu dot org 2007-07-24 19:54 ` dfranke at gcc dot gnu dot org 2007-07-24 19:59 ` dfranke at gcc dot gnu dot org 2007-07-24 20:51 ` dfranke at gcc dot gnu dot org 2007-07-26 4:03 ` jvdelisle at gcc dot gnu dot org 2007-07-26 4:54 ` jvdelisle at gcc dot gnu dot org 2007-07-26 4:56 ` jvdelisle at gcc dot gnu dot org [this message] 2007-07-26 6:58 ` dfranke at gcc dot gnu dot org 2007-07-27 5:47 ` patchapp at dberlin dot org 2007-07-27 16:30 ` jvdelisle at gcc dot gnu dot org 2007-07-27 16:34 ` jvdelisle at gcc dot gnu dot org 2007-07-27 16:53 ` jvdelisle at gcc dot gnu dot org 2008-01-22 23:19 ` anlauf at gmx dot de 2008-01-22 23:42 ` burnus at gcc dot gnu dot org 2008-01-23 15:59 ` [Bug fortran/32760] [4.3 Regression] " burnus at gcc dot gnu dot org 2008-01-23 16:47 ` burnus at gcc dot gnu dot org 2008-01-24 7:04 ` jvdelisle at gcc dot gnu dot org 2008-01-24 8:08 ` jvdelisle at gcc dot gnu dot org 2008-01-24 15:13 ` burnus at gcc dot gnu dot org 2008-01-24 15:22 ` burnus at gcc dot gnu dot org 2008-01-31 23:22 ` pault at gcc dot gnu dot org 2008-02-01 6:01 ` pault at gcc dot gnu dot org 2008-02-01 9:35 ` burnus at gcc dot gnu dot org 2008-02-02 21:32 ` dominiq at lps dot ens dot fr 2008-02-03 11:11 ` dominiq at lps dot ens dot fr 2008-02-03 11:31 ` pault at gcc dot gnu dot org 2008-02-03 11:32 ` pault 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=20070726045619.28479.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).