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 libfortran/15234] libgfortran doesn't compile on Tru64 4.0f UNIX
Date: Thu, 18 Nov 2004 12:18:00 -0000	[thread overview]
Message-ID: <20041118121822.25575.qmail@sourceware.org> (raw)
In-Reply-To: <20040430190236.15234.ro@techfak.uni-bielefeld.de>


------- Additional Comments From pinskia at gcc dot gnu dot org  2004-11-18 12:18 -------
5.1 is fixed but 4.0 is still broken.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
  GCC build triplet|alpha-dec-osf5.1b           |
   GCC host triplet|alpha-dec-osf5.1b           |
 GCC target triplet|alpha-dec-osf5.1b           |alpha-dec-osf4.0f
            Summary|libgfortran doesn't compile |libgfortran doesn't compile
                   |on Tru64 UNIX               |on Tru64 4.0f UNIX


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15234


  parent reply	other threads:[~2004-11-18 12:18 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-30 19:20 [Bug fortran/15234] New: [tree-ssa] libgfortran doesn't compile on Tru64 UNIX gcc-bugzilla at gcc dot gnu dot org
2004-04-30 19:34 ` [Bug libfortran/15234] " pinskia at gcc dot gnu dot org
2004-05-07  9:03 ` cvs-commit at gcc dot gnu dot org
2004-05-07  9:09 ` steven at gcc dot gnu dot org
2004-05-07  9:11 ` steven at gcc dot gnu dot org
2004-05-10 13:59 ` ro at techfak dot uni-bielefeld dot de
2004-05-10 13:59 ` ro at techfak dot uni-bielefeld dot de
2004-05-10 14:09 ` ro at gcc dot gnu dot org
2004-05-14  9:54 ` [Bug libfortran/15234] [gfortran] " pinskia at gcc dot gnu dot org
2004-05-15 12:27 ` tobi at gcc dot gnu dot org
2004-05-16 21:45 ` cvs-commit at gcc dot gnu dot org
2004-05-16 21:46 ` tobi at gcc dot gnu dot org
2004-05-16 22:04 ` pinskia at gcc dot gnu dot org
2004-05-18  1:17 ` ro at techfak dot uni-bielefeld dot de
2004-05-18  5:08 ` ro at techfak dot uni-bielefeld dot de
2004-05-18 10:36 ` ro at techfak dot uni-bielefeld dot de
2004-05-18 11:45 ` pinskia at gcc dot gnu dot org
2004-05-18 23:20 ` ro at techfak dot uni-bielefeld dot de
2004-05-19  5:11 ` tobi at gcc dot gnu dot org
2004-05-27 21:08 ` cvs-commit at gcc dot gnu dot org
2004-07-15 14:53 ` [Bug libfortran/15234] " cvs-commit at gcc dot gnu dot org
2004-07-15 15:03 ` tobi at gcc dot gnu dot org
2004-08-04  7:20 ` pinskia at gcc dot gnu dot org
2004-08-11 21:56 ` pinskia at gcc dot gnu dot org
2004-11-18 11:32 ` paul dot richard dot thomas at cea dot fr
2004-11-18 12:18 ` pinskia at gcc dot gnu dot org [this message]
2004-11-20 15:45 ` [Bug libfortran/15234] libgfortran doesn't compile on Tru64 UNIX V4.0F pinskia at gcc dot gnu dot org
2004-12-01 18:15 ` mmitchel at gcc dot gnu dot org
2005-01-06 14:40 ` tobi at gcc dot gnu dot org
2005-06-13 16:04 ` fxcoudert at gcc dot gnu dot org
2005-07-19 10:32 ` fxcoudert at gcc dot gnu dot org
2005-08-16 19:28 ` tobi at gcc dot gnu dot org
2005-08-16 19:34 ` ro at techfak dot uni-bielefeld dot de
2005-08-17  2:24 ` pinskia at gcc dot gnu dot org
2005-09-05 10:43 ` fxcoudert at gcc dot gnu dot org
2005-09-22 17:50 ` fxcoudert 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=20041118121822.25575.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: link
Be 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).