public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Edelsohn <dje.gcc@gmail.com>
To: Richard Biener <rguenther@suse.de>,
	Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: genmatch infinite loop during bootstrap on AIX
Date: Sat, 25 Oct 2014 15:16:00 -0000	[thread overview]
Message-ID: <CAGWvny=ghm7XKQ6y8oMhQDG1Ru=Si8wqorr6nHrAirp02P6pag@mail.gmail.com> (raw)
In-Reply-To: <A9E6708C-0B2E-4925-A30C-62D88990DBC6@suse.de>

It may be fallout from Maxim's scheduler patch.  I'm testing that.
Backing up before Maxim's patch and your genmatch patch does not enter
an endless loop.

- David

On Sat, Oct 25, 2014 at 4:06 AM, Richard Biener <rguenther@suse.de> wrote:
> On October 25, 2014 1:33:39 AM CEST, David Edelsohn <dje.gcc@gmail.com> wrote:
>>genmatch is hanging when bootstrapping on AIX (gcc111).  When I attach
>>to the process:
>>
>>#0  0x1007efac in std::basic_string<char, std::char_traits<char>,
>>std::allocator<char> >::basic_string ()
>>#1  0x1000e6b0 in _ZN6parser13parse_captureEP7operand (this=0x300594b8,
>>op=0x0)
>>    at /home/dje/src/src/gcc/genmatch.c:2607
>
> Does it really hang in libstdc++ or does it loop somewhere in genmatch? Is this stage1 or later?
>
> Does this happen only after the 2nd part of the merge went in? That is, what revision?
>
> Thanks,
> Richard.
>
>>#2  0x1000e9f0 in _ZN6parser10parse_exprEv (this=0x2ff20208)
>>    at /home/dje/src/src/gcc/genmatch.c:2669
>>#3  0x1000ee38 in _ZN6parser8parse_opEv (this=0x2ff20208)
>>    at /home/dje/src/src/gcc/genmatch.c:2728
>>#4  0x1000efc4 in
>>_ZN6parser14parse_simplifyEjR3vecIP8simplify7va_heap6vl_ptrEP12predicate_idP4expr
>>(this=0x2ff20208, match_location=4614, simplifiers=...,
>>    matcher=0x0, result=0x0) at /home/dje/src/src/gcc/genmatch.c:2792
>>#5  0x100102fc in _ZN6parser13parse_patternEv (this=0x2ff20208)
>>    at /home/dje/src/src/gcc/genmatch.c:3052
>>#6  0x10010c0c in _ZN6parser9parse_forEj (this=0x2ff20208)
>>    at /home/dje/src/src/gcc/genmatch.c:2991
>>#7  0x10010350 in _ZN6parser13parse_patternEv (this=0x2ff20208)
>>    at /home/dje/src/src/gcc/genmatch.c:3090
>>#8  0x1001122c in _ZN6parserC2EP10cpp_reader (this=0x2ff20208,
>>r_=0x3003bbec)
>>    at /home/dje/src/src/gcc/genmatch.c:3122
>>#9  0x10004acc in main (argc=<error reading variable>,
>>    argv=<error reading variable>) at  _start_ :3204
>
>

  parent reply	other threads:[~2014-10-25 14:05 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 [this message]
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
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='CAGWvny=ghm7XKQ6y8oMhQDG1Ru=Si8wqorr6nHrAirp02P6pag@mail.gmail.com' \
    --to=dje.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=maxim.kuvyrkov@linaro.org \
    --cc=rguenther@suse.de \
    /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).