This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: [PATCH] Merging Cilk Plus into Trunk (Patch 1 of approximately 22)



>-----Original Message-----
>From: Andi Kleen [mailto:andi@firstfloor.org]
>Sent: Friday, September 07, 2012 1:05 PM
>To: Iyer, Balaji V
>Cc: Richard Guenther; gcc-patches@gcc.gnu.org; Gabriel Dos Reis; Aldy
>Hernandez (aldyh@redhat.com); Jeff Law; rth@redhat.com
>Subject: Re: [PATCH] Merging Cilk Plus into Trunk (Patch 1 of approximately 22)
>
>"Iyer, Balaji V" <balaji.v.iyer@intel.com> writes:
>>>
>>>The answer is that you should not enable the vectorizer.
>>
>> OK. I will fix that.
>
>It still seems like useful functionality. Otherwise you have to compile the whole
>program with -O3, just to vectoriz a few marked functions or add additional
>annotations for all of them. How about a separate command line flag to auto
>enable vectorization (or -O3) for functions with Cilk vector annotations?

Yes, I really like this idea and that is kind of what I want. But, how do I turn on vectorization on a function by function basis? I tried to set flag_tree_vectorize=1 but that doesn't seem to do the trick.

>
>-Andi
>
>--
>ak@linux.intel.com -- Speaking for myself only


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]