[llvm] r258208 - [Orc] Oops - lambda capture changed in r258206 was correct.

[Tobias Grosser via llvm-commits]

On 01/19/2016 11:32 PM, Lang Hames via llvm-commits wrote:
> Author: lhames
> Date: Tue Jan 19 16:32:58 2016
> New Revision: 258208
>
> URL: http://llvm.org/viewvc/llvm-project?rev=258208&view=rev
> Log:
> [Orc] Oops - lambda capture changed in r258206 was correct.

Dearl Lang,

I now see the following segfaults with gcc 4.7.2:

/home/grosser/buildslave/perf-x86_64-penryn-O3-polly-unprofitable/llvm.src/lib/ExecutionEngine/Orc/OrcMCJITReplacement.cpp: 
In lambda function:
/home/grosser/buildslave/perf-x86_64-penryn-O3-polly-unprofitable/llvm.src/lib/ExecutionEngine/Orc/OrcMCJITReplacement.cpp:128:1: 
internal compiler error: in get_expr_operands, at tree-ssa-operands.c:1035
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.7/README.Bugs> for instructions.
/home/grosser/buildslave/perf-x86_64-penryn-O3-polly-unprofitable/llvm.src/lib/ExecutionEngine/Orc/OrcCBindingsStack.cpp: 
In lambda function:
/home/grosser/buildslave/perf-x86_64-penryn-O3-polly-unprofitable/llvm.src/lib/ExecutionEngine/Orc/OrcCBindingsStack.cpp:43:1: 
internal compiler error: in get_expr_operands, at tree-ssa-operands.c:1035
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.7/README.Bugs> for instructions.
/home/grosser/buildslave/perf-x86_64-penryn-O3-polly-unprofitable/llvm.src/lib/ExecutionEngine/Orc/OrcCBindings.cpp: 
In lambda function:
/home/grosser/buildslave/perf-x86_64-penryn-O3-polly-unprofitable/llvm.src/lib/ExecutionEngine/Orc/OrcCBindings.cpp:97:1: 
internal compiler error: in get_expr_operands, at tree-ssa-operands.c:1035
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.7/README.Bugs> for instructions.

It is clearly an older GCC version, but we still list is as documented.
Could you possibly fix/revert the offending patch (or otherwise 
officially propose we move to a newer gcc version)?

Thank you,
Tobias