On Sun, Oct 14, 2012 at 1:40 AM, Andrew Pinski wrote:
Maybe Ian can mention why he used alloca there instead of xmalloc.
It was a long time ago, but I expect it was just because alloca is
usually fine for memory that has to live for just a single function.
As a single-threaded program, GCC do
On Sun, Oct 14, 2012 at 1:40 AM, Andrew Pinski wrote:
>
> Maybe Ian can mention why he used alloca there instead of xmalloc.
It was a long time ago, but I expect it was just because alloca is
usually fine for memory that has to live for just a single function.
As a single-threaded program, GCC do
Andrew Pinski Wrote:
>> I figured out that ifcvt.c uses alloca to reserve mem on the stack. this is
>> the point where the segmentation fault occurs.
>
> It is also a regression from what I can tell too from 4.1.x.
And one that's fixed for GCC 4.8.
See http://gcc.gnu.org/ml/gcc-patches/2012-08/msg
On Sun, Oct 14, 2012 at 1:05 AM, thorsten wrote:
> Hello all,
>
> this might be a noob Question but perhaps someone is so kind as to shed some
> light...
>
> using gcc-4.5.4 to build large files (as in wireshark or qemu) with
> Optimizations enabled (in my case -O2 -pipe -march=core2
> -fomit-fram
Hello all,
this might be a noob Question but perhaps someone is so kind as to shed
some light...
using gcc-4.5.4 to build large files (as in wireshark or qemu) with
Optimizations enabled (in my case -O2 -pipe -march=core2
-fomit-frame-pointer) I get segmentation faults due to Stack limits,
