public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
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>
Subject: Re: genmatch infinite loop during bootstrap on AIX
Date: Mon, 27 Oct 2014 14:32:00 -0000	[thread overview]
Message-ID: <CAGWvnymYFhYiK_d58izEoXXX5hZJ+uM8eu_Tbe=pZ=v+j9xxVw@mail.gmail.com> (raw)
In-Reply-To: <C3399E76-42FD-47B0-87CA-2F24C36B930F@gmail.com>

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...

gcc111 uses GCC 4.8.1 as the default version of GCC.  That bootstrap
fails in stage 2.

My internal system has GCC 4.7.3 installed.  That bootstrap fails in stage 1.

>
> Bah.
>
> The place where it is looping is using std::map <std::string, unsigned>.

I hope that this isn't a signed char issue.

> Does -static-libstdc++ work for you host compilers?

Yes, GCC uses -static-libstdc++ on AIX.

> Can you try emptying gcc/match.pd for a non-working rev.?

An empty match.pd seems to work.  I will try adding back stanzas and
see where it hangs.

Thanks, David

  reply	other threads:[~2014-10-27 14:32 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-24 23:37 David Edelsohn
2014-10-25  8:08 ` Richard Biener
2014-10-25 14:05   ` David Edelsohn
2014-10-25 15:16   ` David Edelsohn
2014-10-25 17:40     ` David Edelsohn
     [not found]       ` <CAGWvnynWYR5FYctJTa2GGvwGo3asvkU23Y-7Om8pLqCT3w-52A@mail.gmail.com>
2014-10-26  6:40         ` David Edelsohn
2014-10-26 10:37           ` Richard Biener
2014-10-27  1:36             ` David Edelsohn
2014-10-27  7:48               ` Richard Biener
2014-10-27 14:32                 ` David Edelsohn [this message]
2014-10-27 14:56                 ` David Edelsohn
2014-10-27 19:28                 ` David Edelsohn
2014-10-27 20:13                   ` Richard Biener
2014-10-27 23:36                     ` David Edelsohn
2014-10-28  8:43                       ` Richard Biener
2014-10-29 12:54 ` Richard Biener
2014-10-29 13:23   ` David Edelsohn
2014-10-29 13:31     ` Richard Biener
2014-10-29 17:31       ` David Edelsohn
2014-10-30  8:54         ` Richard Biener
2014-10-30 14:29           ` David Edelsohn
2014-10-31  8:54             ` Richard Biener

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='CAGWvnymYFhYiK_d58izEoXXX5hZJ+uM8eu_Tbe=pZ=v+j9xxVw@mail.gmail.com' \
    --to=dje.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=rguenther@suse.de \
    --cc=richard.guenther@gmail.com \
    /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).