[Bug target/61737] ICE when building libgcc for cris cross-compiler

["hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>]

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

--- Comment #8 from Hans-Peter Nilsson <hp at gcc dot gnu.org> ---
(In reply to dhowells@redhat.com from comment #0)
> ../../../gcc-4.9.0-20140702/libgcc/libgcc2.c: In function ‘__subvsi3’:
> ../../../gcc-4.9.0-20140702/libgcc/libgcc2.c:122:1: error: unrecognizable
> insn:
>  }
>  ^
> (call_insn 27 26 28 7 (parallel [
>             (call (mem:QI (symbol_ref:SI ("abort") [flags 0x41]
> <function_decl 0x7f5784e05d00 abort>) [0 __builtin_abort S1 A8])


This symbol_ref must be wrapped inside a CONST by the middle-end.
Something changed such that that doesn't happen anymore; that's the bug.
Unless this was a deliberate general change in representation, which I doubt.
Still investigating...
>From gcc-bugs-return-456340-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 15 02:48:46 2014
Return-Path: <gcc-bugs-return-456340-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9172 invoked by alias); 15 Jul 2014 02:48:40 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 9002 invoked by uid 48); 15 Jul 2014 02:48:25 -0000
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/61632] Memory corruption on error when writing formatted data
Date: Tue, 15 Jul 2014 02: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: 4.8.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jvdelisle at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jvdelisle at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-61632-4-lNKGUtzNVV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61632-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61632-4@http.gcc.gnu.org/bugzilla/>
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: 2014-07/txt/msg00931.txt.bz2
Content-length: 625

https://gcc.gnu.org/bugzilla/show_bug.cgi?ida632

--- Comment #14 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---

(In reply to Dominique d'Humieres from comment #10)

--- snip ---
>
> Is the printing of 'YYY' supposed to happen?

Its sort of like Steve said earlier.  The coder is choosing to ignore an error
condition so anything gfortran does is valid.  In this case the output got
wriiten to buffer before the error occurred.  You are bypassing all of the
normal error handling when you do this. The buffer got flushed.

Its not worth the time to change any of it really.

The program should exit, its invalid.