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 target/15266] libgfortran doesn't compile on IRIX 5.3
Date: Mon, 05 Sep 2005 13:53:00 -0000 [thread overview]
Message-ID: <20050905135322.16434.qmail@sourceware.org> (raw)
In-Reply-To: <20040503154240.15266.ro@techfak.uni-bielefeld.de>
------- Additional Comments From pinskia at gcc dot gnu dot org 2005-09-05 13:53 -------
(In reply to comment #19)
> Now fixed for 4.0 branch, commit for 3.4.5 still pending. This does not concern
> libgfortran any more, but there's no fixincludes component, so I don't know what
> to do...
It should be put into the target component since almost always fixincludes are target dependent.
--
What |Removed |Added
----------------------------------------------------------------------------
Component|libfortran |target
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15266
next prev parent reply other threads:[~2005-09-05 13:53 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-03 15:42 [Bug fortran/15266] New: [tree-ssa] " gcc-bugzilla at gcc dot gnu dot org
2004-05-03 15:50 ` [Bug libfortran/15266] " pinskia at gcc dot gnu dot org
2004-05-03 16:11 ` ro at techfak dot uni-bielefeld dot de
2004-05-18 11:45 ` [Bug libfortran/15266] [gfortran] " pinskia at gcc dot gnu dot org
2004-05-18 23:18 ` ro at techfak dot uni-bielefeld dot de
2004-08-11 21:56 ` [Bug libfortran/15266] " pinskia at gcc dot gnu dot org
2004-12-27 15:09 ` pinskia at gcc dot gnu dot org
2005-01-06 14:40 ` tobi at gcc dot gnu dot org
2005-01-07 0:16 ` coudert at clipper dot ens dot fr
2005-01-09 15:02 ` coudert at clipper dot ens dot fr
2005-01-09 15:07 ` Tobias dot Schlueter at physik dot uni-muenchen dot de
2005-02-20 21:24 ` pinskia at gcc dot gnu dot org
2005-04-16 22:33 ` pinskia at gcc dot gnu dot org
2005-06-09 18:53 ` ro at techfak dot uni-bielefeld dot de
2005-06-13 16:10 ` fxcoudert at gcc dot gnu dot org
2005-06-15 0:00 ` cvs-commit at gcc dot gnu dot org
2005-06-15 0:01 ` ro at gcc dot gnu dot org
2005-06-15 0:02 ` ro at gcc dot gnu dot org
2005-06-15 8:22 ` Tobias dot Schlueter at physik dot uni-muenchen dot de
2005-06-15 9:30 ` ro at techfak dot uni-bielefeld dot de
2005-06-15 9:37 ` Tobias dot Schlueter at physik dot uni-muenchen dot de
2005-07-08 1:37 ` mmitchel at gcc dot gnu dot org
2005-07-19 11:14 ` fxcoudert at gcc dot gnu dot org
2005-08-19 14:55 ` cvs-commit at gcc dot gnu dot org
2005-09-05 10:41 ` fxcoudert at gcc dot gnu dot org
2005-09-05 13:53 ` pinskia at gcc dot gnu dot org [this message]
2005-09-27 18:21 ` [Bug target/15266] " 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=20050905135322.16434.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).