On Mon, Sep 21, 2015 at 8:17 PM, Marc Glisse wrote:
> On Mon, 21 Sep 2015, Daniel Gutson wrote:
>
>> This is derived from https://gcc.gnu.org/ml/gcc-help/2015-03/msg00091.html
>>
>> Currently, gcc provides an optimization that transforms a call to
>> malloc and a call to memset into a call to call
On Mon, Sep 21, 2015 at 2:26 PM, Andrew Pinski wrote:
> On Mon, Sep 21, 2015 at 10:20 AM, Daniel Gutson
> wrote:
>> This is derived from https://gcc.gnu.org/ml/gcc-help/2015-03/msg00091.html
>>
>> Currently, gcc provides an optimization that transforms a call to
>> malloc and a call to memset int
On Mon, Sep 21, 2015 at 3:33 PM, Daniel Gutson
wrote:
> On Mon, Sep 21, 2015 at 2:26 PM, Andrew Pinski wrote:
>> On Mon, Sep 21, 2015 at 10:20 AM, Daniel Gutson
>> wrote:
>>> This is derived from https://gcc.gnu.org/ml/gcc-help/2015-03/msg00091.html
>>>
>>> Currently, gcc provides an optimizatio
On Mon, 21 Sep 2015, Daniel Gutson wrote:
This is derived from https://gcc.gnu.org/ml/gcc-help/2015-03/msg00091.html
Currently, gcc provides an optimization that transforms a call to
malloc and a call to memset into a call to calloc.
This is fine except when it takes place within the calloc() f
On Mon, Sep 21, 2015 at 10:26:23AM -0700, Andrew Pinski wrote:
> On Mon, Sep 21, 2015 at 10:20 AM, Daniel Gutson
> wrote:
> > This is derived from https://gcc.gnu.org/ml/gcc-help/2015-03/msg00091.html
> >
> > Currently, gcc provides an optimization that transforms a call to
> > malloc and a call t
On Mon, Sep 21, 2015 at 10:20 AM, Daniel Gutson
wrote:
> This is derived from https://gcc.gnu.org/ml/gcc-help/2015-03/msg00091.html
>
> Currently, gcc provides an optimization that transforms a call to
> malloc and a call to memset into a call to calloc.
> This is fine except when it takes place w
