Displaying 3 results from an estimated 3 matches for "wepskn".
Did you mean:
epson
2018 Jun 19
6
Naming clash: -DCLS=n and CLS in code
...re suggesting, and Clang is not that weird library.
This is from a famous article series titled "What every programmer should know
about memory":
gcc -DCLS=$(getconf LEVEL1_DCACHE_LINESIZE) ...
https://lwn.net/Articles/255364/
http://mosermichael.github.io/cstuff/all/blog/2015/12/11/wepskn.html
https://www.dcl.hpi.uni-potsdam.de/teaching/numasem/slides/NUMASem_Matrix_multiplication.pdf
You can find more examples by searching for "DCLS getconf LEVEL1_DCACHE_LINESIZE".
2018 Jun 19
3
Naming clash: -DCLS=n and CLS in code
...;
>>
>> This is from a famous article series titled "What every programmer should know about memory":
>> gcc -DCLS=$(getconf LEVEL1_DCACHE_LINESIZE) ...
>>
>> https://lwn.net/Articles/255364/
>> http://mosermichael.github.io/cstuff/all/blog/2015/12/11/wepskn.html
>> https://www.dcl.hpi.uni-potsdam.de/teaching/numasem/slides/NUMASem_Matrix_multiplication.pdf
>>
>> You can find more examples by searching for "DCLS getconf LEVEL1_DCACHE_LINESIZE".
>>
>>
>>
>> _____________________________________________...
2018 Jun 19
2
Naming clash: -DCLS=n and CLS in code
Tim Northover via llvm-dev wrote on 06/19/2018 07:55 PM:
> On Tue, 19 Jun 2018 at 18:22, U.Mutlu via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
>> I think such "reserved" names like CLS that can be passed to the compiler(s),
>> should be avoided as identifiers for naming variables, constants, enum
>> members, macros etc.
>
> Why are you passing