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 <rguent...@suse.de> wrote: > On October 25, 2014 1:33:39 AM CEST, David Edelsohn <dje....@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 > >
