public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/22097] libgfortran build failure on mips-sgi-irix6.5
Date: Tue, 07 Feb 2006 10:12:00 -0000	[thread overview]
Message-ID: <20060207101211.26253.qmail@sourceware.org> (raw)
In-Reply-To: <bug-22097-10259@http.gcc.gnu.org/bugzilla/>



------- Comment #17 from fxcoudert at gcc dot gnu dot org  2006-02-07 10:12 -------
(In reply to comment #15)
> There is one open question. Is the "#ifdef __sgi__" the right way to
> distinguish between IRIX and other mips systems?
> This patch applies cleanly to 4.1 and mainline.
> I ask for comments.

Looking at config.guess and other occurences of __sgi__ in the gcc source, I
think it's the right way.

Submit the patch on the gcc, gcc-patches and fortran along with the question,
and if there is no objection from the mips maintainers in the next few days,
I'll approve it.

Thanks for the patch!


-- 

fxcoudert at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |patch


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


  parent reply	other threads:[~2006-02-07 10:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-22097-10259@http.gcc.gnu.org/bugzilla/>
2005-10-23 13:15 ` [Bug libfortran/22097] " fxcoudert at gcc dot gnu dot org
2005-10-23 13:18 ` fxcoudert at gcc dot gnu dot org
2005-10-23 21:27 ` wilson at gcc dot gnu dot org
2005-10-24  9:33 ` fxcoudert at gcc dot gnu dot org
2005-10-25 20:09 ` pinskia at gcc dot gnu dot org
2005-11-10 15:35 ` fxcoudert at gcc dot gnu dot org
2006-01-04 12:14 ` [Bug target/22097] " fxcoudert at gcc dot gnu dot org
2006-01-12 13:08 ` fxcoudert at gcc dot gnu dot org
2006-02-02 18:01 ` r dot emrich at de dot tecosim dot com
2006-02-02 19:18 ` fxcoudert at gcc dot gnu dot org
2006-02-06 17:58 ` r dot emrich at de dot tecosim dot com
2006-02-07  9:55 ` r dot emrich at de dot tecosim dot com
2006-02-07 10:00 ` r dot emrich at de dot tecosim dot com
2006-02-07 10:12 ` fxcoudert at gcc dot gnu dot org [this message]
2006-02-07 16:35 ` r dot emrich at de dot tecosim dot com
2006-03-08  9:51 ` 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=20060207101211.26253.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).