(This is a copy of https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70078)
I'd like to clean up this documentation issue, but need some help:
Dominik Vogt 2016-03-04 11:05:16 UTC
> The section "Defining How to Split Instructions" in the gccint
> manual claims
>
> The preparation-statements are simi
Hi,
On Thu, 10 Mar 2016, Richard Biener wrote:
> Then I'd like to be able to re-construct SSA without jumping through
> hoops (usually you can get close but if you require copies propagated in
> a special way you are basically lost for example).
>
> Thus my proposal to make the GSoC student at
On March 14, 2016 4:31:57 PM GMT+01:00, Andrey Tarasevich
wrote:
>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
> On Mar 14, 2016, at 12:05 PM, C Bergström wrote:
>
> I don't speak with any community authority - I think your test tool is
> 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 be
On Mon, 2016-03-14 at 16:31 +0100, Andrey Tarasevich wrote:
> 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
Yes.
> or source files of siz
Yeah, I guess attempt to commit a C file with 700K lines of code won’t end well
for a developer.
Thanks for clarifying things!
> On 14 Mar 2016, at 17:05, C Bergström wrote:
>
> I don't speak with any community authority - I think your test tool is
> misconfigured then. I don't see any pragmat
I don't speak with any community authority - I think your test tool is
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, 201
99% of 700k, 693k of printf(), is it ascii art ?
++t
> Le 14 Mar 2016 à 16:42, paul_kon...@dell.com a écrit :
>
>
>> On Mar 14, 2016, at 11:31 AM, Andrey Tarasevich
>> wrote:
>>
>> Hi,
>>
>> I have a source file with 700k lines of code 99% of which are printf()
>> statements. Compiling this
> On 14 Mar 2016, at 16:39, C Bergström wrote:
>
> On Mon, Mar 14, 2016 at 11:31 PM, Andrey Tarasevich
> wrote:
>> 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 suc
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 wrote:
>
> also cross-checked with clang 3.8?
>
> Am 14.03.2016 um 16:31 schrieb Andrey Tarasevich:
>> Hi,
>>
>> I have a source file with 700k lines of code 99% of
> On Mar 14, 2016, at 11:31 AM, Andrey Tarasevich
> wrote:
>
> 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
On Mon, Mar 14, 2016 at 11:31 PM, Andrey Tarasevich
wrote:
> 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 a
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 Ubuntu
On Fri, Mar 11, 2016 at 6:46 PM, H.J. Lu wrote:
> On Fri, Mar 11, 2016 at 6:45 AM, H.J. Lu wrote:
>> On Fri, Mar 11, 2016 at 6:03 AM, Richard Biener
>> wrote:
>>> On Fri, Mar 11, 2016 at 3:01 PM, H.J. Lu wrote:
On Fri, Mar 11, 2016 at 5:50 AM, H.J. Lu wrote:
> On Fri, Mar 11, 2016 at
14 matches
Mail list logo
