Re:Results of the Grand C++ Error Explosion Competition
by simcop2387 on Thursday May 15, 2014 @01:52PM
(#7751049)
I am really impressed at the winner of the biggest error. It's incredible how much it produces. Right now I'm testing it and running it through pv to see how many errors it makes. Right now on my machine it's producing errors at a rate of 74MB/s. I never thought I'd look at errors in rates of bytes/time.
[ Parent
| on HN ]
Re:Results of the Grand C++ Error Explosion Competition
by Morgawr on Thursday May 15, 2014 @01:59PM
(#7751085)
I ran it for a couple of minutes piped to a log file to catch the errors, I had to kill it because the file was becoming too big. When I closed it, it was 4.9GB (and still growing).
Amazing.
Re:Results of the Grand C++ Error Explosion Competition
by simcop2387 on Thursday May 15, 2014 @02:21PM
(#7751225)
I've had it running a while with wc and pv, so far it's up to 130GB after half an hour. I'm REALLY impressed by it.
$ g++ -o jeh jeh.cpp 2>&1 | pv | wc
131GB 0:30:15 [71.7MB/s]
Re:Results of the Grand C++ Error Explosion Competition
by blt on Thursday May 15, 2014 @02:34PM
(#7751309)
It errors instantly on MSVC 2013.
fatal error C1014: too many include files : depth = 1024
Re:Results of the Grand C++ Error Explosion Competition
by Alekanekelo on Thursday May 15, 2014 @04:27PM
(#7752034)
A similar thing happens to clang (Apple LLVM version 5.1 (clang-503.0.40)) which gives the following error message:
fatal error: too many errors emitted, stopping now [-ferror-limit=]
According to the User's manual the default is 20 for -ferror-limit [1].
Re:Results of the Grand C++ Error Explosion Competition
by simcop2387 on Thursday May 15, 2014 @02:43PM
(#7751370)
That actually sounds reasonable to me. GCC producing 230GB of error messages is definitely excessive. If it ever completes I'll update here with the actual final count of the length of the error message.
Re:Results of the Grand C++ Error Explosion Competition
by simcop2387 on Thursday May 15, 2014 @07:03PM
(#7752796)
Ok, it's been running all day while I've been working. I don't think it's going to ever complete. I'm at 1.32 TB of output from it. I can't overstate how impressed I am by that. If it completes before I leave then I'll start it again but run it through a compressor and hope I don't fill up my disk. It was large strings of //.//. so i think it should compress well and I'll upload it somewhere for someone to look at.
Re:Results of the Grand C++ Error Explosion Competition
by jleader on Thursday May 15, 2014 @03:08PM
(#7751506)
It's been a while since I've done much c++, and google has failed me. What is pv?
Re:Results of the Grand C++ Error Explosion Competition
by eshyong on Thursday May 15, 2014 @03:21PM
(#7751592)
Looks like this is what you're looking for:
"pv - monitor the progress of data through a pipe"
Re:Results of the Grand C++ Error Explosion Competition
by jleader on Thursday May 15, 2014 @08:24PM
(#7753114)
Yes, thanks! I was originally searching for "c++ pv", which led to lots of c++ examples implementing "present value" calculators, or snippets of code using "pv" as a variable name. I later tried "pv tarball" (figuring that a useful command-line utility would probably be downloadable that way), which led me to http://www.catonmat.net/blog/unix-utilities-pipe-viewer/ and so to http://www.ivarch.com/programs/pv.shtml.