On Mon, Aug 22, 2016 at 11:54 PM, lhmouse <lh_mouse@xxxxxxx> wrote: > Got 6.2 and tried it. No ICE. > Perhaps the bug occurs on trunk only. Ah yes -- I think I recall now (just rebuilt 6.1 on my end, no ICE for the reported -Wall bug). I was having unrelated issues with 6.1 (from distant memory, if using precompiled header, c++ compiler would exit early and silently when building the final exe). I was going to experiment with things like -Wall, -Winvalid-pch, -v, -H options, anonymous spaces, etc. and also to see whether the trunk had exhibited the same problem for me (presumption being that there is a bug in my code or my gcc build which triggers the observed behavior)... and then I hit the -Wall bug on trunk and by the time I had found a moment to reduce the test case I had forgotten that -Wall wasn't necessarily buggy in 6.1 etal :) mea culpa :) > That is also why > I don't build development versions. I agree... well, mostly for the production runs... for other cases I'm not against it (the more play the trunk receives the more chances for the bugs to be discovered and ironed out earlier :) ... presuming one has the time of course :) > E:\Desktop>g++ -v [...] > Thread model: mcf [...] Interesting, thanks! Learned something new today -- the mcf threading model :) I'll read up on it :) > > > ------------------ > Best regards, > lh_mouse > 2016-08-22 > > ------------------------------------------------------------- > 发件人：leon zadorin <leonleon77@xxxxxxxxx> > 发送日期：2016-08-22 21:24 > 收件人：gcc-help > 抄送： > 主题：Re: GCC ICE bug with segfault... > > On Mon, Aug 22, 2016 at 6:58 PM, lhmouse <lh_mouse@xxxxxxx> wrote: >> Unreproducible on 6.1.0 targeting either i686 or x86_64. > > Thanks for testing on 6.1.0 :) > Just out of curiosity, which host/target triplet your gcc is > configured for and what are the rest of its "configured with" options? > I'm building mine on Windows 7 as x86_64-w64-mingw32 (I'll also try > with recently released 6.2, but just so that I can cross-reference my > config parameters with yours when I build 6.1/6.2/trunk it'd be good > to know your config params/etc). > >> In order to make a *minimal* testcase, please remove unrelated stuff, >> such as redundant `#include`s. For example, you can run >> `g++ -E -o foo.cc` to get a preprocessed source file then >> cut unrelated code off. > > Sounds good -- thanks for the advise! > > Kind regarsd > Leon. >
