[llvm-commits] [PATCH/RFC] Loop Data Software Prefetching
Hal Finkel
hfinkel at anl.gov
Thu Jan 31 07:32:32 PST 2013
----- Original Message -----
> From: "Arnold Schwaighofer" <aschwaighofer at apple.com>
> To: "Hal Finkel" <hfinkel at anl.gov>
> Cc: "Nadav Rotem" <nrotem at apple.com>, "l >> Commit Messages and Patches for LLVM" <llvm-commits at cs.uiuc.edu>
> Sent: Thursday, January 31, 2013 9:05:23 AM
> Subject: Re: [llvm-commits] [PATCH/RFC] Loop Data Software Prefetching
>
>
> On Jan 31, 2013, at 8:59 AM, Hal Finkel <hfinkel at anl.gov> wrote:
>
> >> You might be right that this is a non-problem, but it seems fairly
> >> cumbersome. For prefetching distance, unrolling threshold, etc. we
> >> could move the default value into NOTTI, make the default value of
> >> the command line parameter 0 (or -1 or something else invalid),
> >> and
> >> then use the TTI value only if the command-line value is invalid.
> >> But how will this work for boolean parameters? Maybe we could make
> >> it possible to determine if a command-line parameter was actually
> >> provided or if it has its default value.
>
> There is Option::getNumOccurrences() which can be used to determine
> whether a parameter was provided.
Thanks! That will work.
-Hal
>
More information about the llvm-commits
mailing list