From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 124359 invoked by alias); 10 Oct 2015 08:48:49 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 120259 invoked by uid 48); 10 Oct 2015 08:48:45 -0000 From: "dominiq at lps dot ens.fr" 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 5.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dominiq at lps dot ens.fr X-Bugzilla-Status: WAITING X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-10/txt/msg00752.txt.bz2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66534 --- Comment #5 from Dominique d'Humieres --- > 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.