public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/66534] Compilation error of gfortran building on YDL6.2
Date: Sat, 10 Oct 2015 08:48:00 -0000	[thread overview]
Message-ID: <bug-66534-4-mvcE0ybA8X@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66534-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66534

--- Comment #5 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> As the result the error above not generated but I see the next bug (See below).
> I am guessing many errors embedded for YDL 6.2, since
> my hardware (Old iBook; Power PC G3 Processor) is very outdated,
> probably nobody wishes to test it except me.

Did you asked yellow dog linux for help?

> One option is that not to fix further bugs for Power PC G3 Processor 
> to save developer's time. This option is OK for me because using
> gfortran on my outdated hardware is not significant.
> Another option is to continue bug fixing to improve gfortran sources.
> Let me know which one is preferable for gfortran developers?

Well, gfortran is built on a quite broad range of platforms without the problem
you report. Unless you tackle the issue yourself, the problem will not be fixed
before the death of your G3! IMO it would be more honest to close this PR as
WONTFIX.


  parent reply	other threads:[~2015-10-10  8:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-14 11:13 [Bug fortran/66534] New: " textdirected at gmail dot com
2015-06-14 11:33 ` [Bug fortran/66534] " schwab@linux-m68k.org
2015-08-30 10:42 ` dominiq at lps dot ens.fr
2015-09-06  8:08 ` textdirected at gmail dot com
2015-10-10  8:48 ` dominiq at lps dot ens.fr [this message]
2015-10-15  5:29 ` textdirected at gmail dot com

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=bug-66534-4-mvcE0ybA8X@http.gcc.gnu.org/bugzilla/ \
    --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).