On Tue, Nov 18, 2014 at 5:33 PM, Thomas Preud'homme
wrote:
>> From: Richard Biener [mailto:richard.guent...@gmail.com]
>> Sent: Monday, November 17, 2014 12:47 PM
>>
>> Hmm. I am a little bit concerned about the malloc traffic generated here.
>> So why not use a vec, get rid of the ->next pointer
> From: Richard Biener [mailto:richard.guent...@gmail.com]
> Sent: Monday, November 17, 2014 12:47 PM
>
> Hmm. I am a little bit concerned about the malloc traffic generated here.
> So why not use a vec, get rid of the ->next pointer and
> use a hash_map to associate the stmt with
> an index int
On Thu, Aug 7, 2014 at 12:55 PM, Thomas Preud'homme
wrote:
> Hi all,
>
> Currently, when an expression doing manual load or bswap is detected, the
> bswap optimization replace it by an actual load and/or bswap instruction
> without considering whether the intermediate values computed in the
> expr
Ping?
> -Original Message-
> From: gcc-patches-ow...@gcc.gnu.org [mailto:gcc-patches-
> ow...@gcc.gnu.org] On Behalf Of Thomas Preud'homme
> Sent: Thursday, August 07, 2014 6:56 PM
> To: gcc-patches@gcc.gnu.org
> Subject: [PATCH] Cancel bswap opt when intermediate s
Hi all,
Currently, when an expression doing manual load or bswap is detected, the
bswap optimization replace it by an actual load and/or bswap instruction
without considering whether the intermediate values computed in the
expressions are reused later. If that is the case, the construction of thes
