[Bug target/63966] [5 regression] inconsistent operand constraints compiling build libcpp

["ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>]

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

--- Comment #6 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #5 from Uroš Bizjak <ubizjak at gmail dot com> ---
> Can you please test this patch:

i386-apple-darwin14.0.0 bootstrap into stage2 now, so seems ok.

Thanks.
        Rainer
>From gcc-bugs-return-467609-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Nov 19 21:14:59 2014
Return-Path: <gcc-bugs-return-467609-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22264 invoked by alias); 19 Nov 2014 21:14:58 -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 22210 invoked by uid 48); 19 Nov 2014 21:14:54 -0000
From: "davem at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/63958] [5 Regression] bootstrap failure in the sanitizer libs on sparc-linux-gnu
Date: Wed, 19 Nov 2014 21:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: davem at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 5.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-63958-4-Nw7pwukoyu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-63958-4@http.gcc.gnu.org/bugzilla/>
References: <bug-63958-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-11/txt/msg02081.txt.bz2
Content-length: 1127

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

davem at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |davem at gcc dot gnu.org

--- Comment #2 from davem at gcc dot gnu.org ---
Can you contribute something other than a knee-jerk reactionary posting of that
submission rules URL?

Those requirements are entirely impractical.  I checked things in directly to
the gcc repo because a sparc gcc-4.9 build failure persisted for 9 months,
which is proof that this proceedure for sanitizer development is completely not
tenable.

A sanitizer developer was CC:'d on the gcc bugzilla in question, and I even
posted a working version of that developers patch and attached it to that bug.
Nothing was done for 4 months after that.

After consulting with Richard Henderson I just checked it in.

And I will continue to do the same in the future, I apologize in advance if
fixing the build in gcc after waiting for upstream to do something about it for
months upsets you.