From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-patches-return-381977-listarch-gcc-patches=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 15355 invoked by alias); 27 Oct 2014 14:37:36 -0000
Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-patches.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-patches/>
List-Post: <mailto:gcc-patches@gcc.gnu.org>
List-Help: <mailto:gcc-patches-help@gcc.gnu.org>
Sender: gcc-patches-owner@gcc.gnu.org
Received: (qmail 15324 invoked by uid 89); 27 Oct 2014 14:37:35 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO: mail-vc0-f176.google.com
Received: from mail-vc0-f176.google.com (HELO mail-vc0-f176.google.com) (209.85.220.176) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Mon, 27 Oct 2014 14:37:34 +0000
Received: by mail-vc0-f176.google.com with SMTP id hq11so2432785vcb.35        for <gcc-patches@gcc.gnu.org>; Mon, 27 Oct 2014 07:37:31 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.220.73.1 with SMTP id o1mr78880vcj.67.1414420651746; Mon, 27 Oct 2014 07:37:31 -0700 (PDT)
Received: by 10.220.73.193 with HTTP; Mon, 27 Oct 2014 07:37:31 -0700 (PDT)
In-Reply-To: <C3399E76-42FD-47B0-87CA-2F24C36B930F@gmail.com>
References: <CAGWvnykRi9tjw4VPpArRaDYYMZvwxjvYt_oqDGMhjmataTLKJA@mail.gmail.com>	<A9E6708C-0B2E-4925-A30C-62D88990DBC6@suse.de>	<CAGWvny=ghm7XKQ6y8oMhQDG1Ru=Si8wqorr6nHrAirp02P6pag@mail.gmail.com>	<CAGWvnym9p7tmE7s2efNW5YjxSDT-vrW-8xJmYzPpRqRodiFGPg@mail.gmail.com>	<CAGWvnynWYR5FYctJTa2GGvwGo3asvkU23Y-7Om8pLqCT3w-52A@mail.gmail.com>	<CAGWvny=Zt44No1-nBWcW+J9_tDSXgFj+-DWAz8NyyzF6kXj-RQ@mail.gmail.com>	<267699E8-43E8-44DA-AA34-2EB99414238C@suse.de>	<CAGWvny=f9Y=3VQC=RjH7x6xw8Xj9ywyCEWx9ec1u=ikhtOx7hw@mail.gmail.com>	<C3399E76-42FD-47B0-87CA-2F24C36B930F@gmail.com>
Date: Mon, 27 Oct 2014 14:56:00 -0000
Message-ID: <CAGWvnyk1Wu9gphsmv_LSyrB=ds6bxeH5-bZguSk-+5GdOGivcg@mail.gmail.com>
Subject: Re: genmatch infinite loop during bootstrap on AIX
From: David Edelsohn <dje.gcc@gmail.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: Richard Biener <rguenther@suse.de>, GCC Patches <gcc-patches@gcc.gnu.org>
Content-Type: text/plain; charset=ISO-8859-1
X-SW-Source: 2014-10/txt/msg02752.txt.bz2

On Mon, Oct 27, 2014 at 2:37 AM, Richard Biener
<richard.guenther@gmail.com> wrote:
> On October 27, 2014 1:49:54 AM CET, David Edelsohn <dje.gcc@gmail.com> wrote:
>>Richi,
>>
>>Does genmatch rely on static constructors or implicitly rely on the
>>order of static constructors? Sometimes those cause problems on AIX.
>
> No, it doesn't.
>
>>Bootstrap on AIX succeeds prior to r216631, e.g., r216624.  It works
>>after your commit r216619 to correct Makefile.in, or prior to that by
>>manually editing Makefile.in to add LIBICONV and LIBINTL.
>
> OK, so this would mean that r216631 causes a miscompile for you. Though that does not match up with you seeing this happening during stage1...
>
> Bah.
>
> The place where it is looping is using std::map <std::string, unsigned>.
>
> Does -static-libstdc++ work for you host compilers?
>
> Can you try emptying gcc/match.pd for a non-working rev.?

Empty file: success.

Header comment: success.

define_predicates stanza: success.

Any "simplify" stanza (with or without "for" loop): HANG.

- David