> misconfigured then. I don't see any pragmatic reason to generate such
> a test. It's unlikely to mirror any real world code and artificial
> test cases like this, at best only serve as some arbitrary data point.
>
> On Mon, Mar 14, 2016 at 11:52 PM, Andrey Tarasevich
> <
> On 14 Mar 2016, at 16:39, C Bergström <cbergst...@pathscale.com> wrote:
>
> On Mon, Mar 14, 2016 at 11:31 PM, Andrey Tarasevich
> <tarasev...@cs.uni-saarland.de> wrote:
>> Hi,
>>
>> I have a source file with 700k lines of code 99% of which are printf(
I cross-checked with Clang 3.7.1. It eats up 4gb of RAM and compiles it under
40sec
> On 14 Mar 2016, at 16:44, Dennis Luehring <dl.so...@gmx.net> wrote:
>
> also cross-checked with clang 3.8?
>
> Am 14.03.2016 um 16:31 schrieb Andrey Tarasevich:
>> Hi,
>>
Hi,
I have a source file with 700k lines of code 99% of which are printf()
statements. Compiling this test case crashes GCC 5.3.0 with segmentation fault.
Can such test case be considered valid or source files of size 35 MB are too
much for a C compiler and it should crash? It crashes on
