This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH][LTO] Committed patch to fix a crash due to syntax error.
On Thu, Oct 9, 2008 at 10:31 AM, Doug Kwan (關振紱) <dougkwan@google.com> wrote:
> 2008/10/9 Richard Guenther <richard.guenther@gmail.com>:
>
>> Sure. Just to clarify - the segfault is with the LTO frontend
>> or with the C++ frontend and -flto? (that is, is the input
>> LTO data or a C++ program?) If the former then I still think
>> this is the wrong approach.
>
> Crash is in the gimplifier. This has nothing to do with LTO except
> that it is found in LTO testing. Input is a C++ source.
Ok. Thanks for the clarification.
Richard.
>>> --bug.cc--
>>> extern bool foo;
>>> void func() { if (foo) { try { return; } catch () {} } }
>>> -------
>>> $ rm -rf bug.s
>>> $ g++ -O2 -S bug.cc /* this is normal, non LTO gcc. */
>>> bug.cc: In function 'void func()':
>>> bug.cc:2: error: expected type-specifier before ')' token
>>
>> So it doesn't crash?
>
> Sorry, 4.0.3 is not a good example. It does not crash since it is not
> tuplified. A not-so-recent copy of trunk, which has the tuples branch
> merged crashes also.
>
>> Richard.
>>
>>> $ cat bug.s
>>> .file "bug.cc"
>>> .ident "GCC: (GNU) 4.0.3 (Ubuntu 4.0.3-1ubuntu5)"
>>> .section .note.GNU-stack,"",@progbits
>>> $
>>>
>>>
>>> 2008/10/9 Richard Guenther <richard.guenther@gmail.com>:
>>>
>>>>
>>>> Does this mean -flto writes out translation units which contain
>>>> errors?
>>>>
>>>
>>
>