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 <[email protected]> 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 <[email protected]> wrote: >> Is it OK to go? >> >> ________________________________ >> From: [email protected] [[email protected]] on >> behalf of Robert Lytton [[email protected]] >> Sent: 02 September 2013 14:26 >> To: [email protected] >> 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 >> [email protected] >> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits >>
_______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
