XCore target: disable vectorization

[Nadav Rotem]

I am not sure what is the right approach here.  Another alternative is to use the TTI interface.  We can wither add a new API for checking if the target benefits from vectorization or we can use this API to check how many vector registers are available:

unsigned TargetVectorRegisters = TTI.getNumberOfRegisters(true);

Thanks,
Nadav


On Sep 6, 2013, at 10:34 AM, Rafael Espíndola <rafael.espindola at gmail.com> wrote:

> I think the idea is OK. Nadav, any objections?
> 
> On the patch itself:
> 
> hasVectorizer is a strange name. disableVectorizerByDefault or
> something else without a "has" would probably be better.
> 
> The two uses of hasVectorizer are in a single function. Can't you put
> its return valuue in a variable and reuse it?
> 
> 
> On 6 September 2013 05:39, Robert Lytton <robert at xmos.com> wrote:
>> Is it OK to go?
>> 
>> ________________________________
>> From: cfe-commits-bounces at cs.uiuc.edu [cfe-commits-bounces at cs.uiuc.edu] on
>> behalf of Robert Lytton [robert at xmos.com]
>> Sent: 02 September 2013 14:26
>> To: cfe-commits at cs.uiuc.edu
>> Subject: XCore target: disable vectorization
>> 
>> Hi,
>> 
>> Here is a patch to disable vectorization for a target by default (only
>> xcore).
>> 
>> Thank you
>> 
>> Robert
>> 
>> 
>> _______________________________________________
>> cfe-commits mailing list
>> cfe-commits at cs.uiuc.edu
>> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
>> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-commits/attachments/20130906/6362c829/attachment.html>