Displaying 4 results from an estimated 4 matches for "_range".
Did you mean:
range
2010 Jan 26
2
[LLVMdev] Returning a structure
...ons in a single cpp file) to write a compiler. In one part of my code, I want to build a function that returns a structure. The LLVM Assembly Language Reference Manual gives this as a possible return value:
> ret { i32, i8 } { i32 4, i8 2 }
Meanwhile, compiling this C function:
> Range make_range(Index location, Index length) {
> return (Range){ location, length };
> }
reveals clang’s IR output to be quite a bit more complex:
> %struct._Range = type <{ i64, i64 }>
>
> define void @make_range(%struct._Range* noalias sret %agg.result, i64 %location, i64 %length) noun...
2009 Dec 21
2
Reading multiple Input Files
...lysis is random i.e. it can be 2, can be 10 or even higher. The R-code I had written (with the guidance of R helpers obviously and I am really grateful to all of you) as of now is sort of hard coding when it comes to reading interest rates as an input e.g.
## INPUT
rate_1 = read.csv('rate1_range.csv')
rate_2 = read.csv('rate2_range.csv')
rate_3 = read.csv('rate3_range.csv')
rate_4 = read.csv('rate4_range.csv')
prob_1 = read.csv('rate1_probs.csv')
prob_2 = read.csv('rate2_probs.csv')
prob_3 = read.csv('rate3_probs.csv')
prob_...
2010 Jan 27
0
[LLVMdev] Returning a structure
...write a compiler. In one part of my code, I want to build a function that returns a structure. The LLVM Assembly Language Reference Manual gives this as a possible return value:
>
>> ret { i32, i8 } { i32 4, i8 2 }
>
> Meanwhile, compiling this C function:
>
>> Range make_range(Index location, Index length) {
>> return (Range){ location, length };
>> }
>
> reveals clang’s IR output to be quite a bit more complex:
>
>> %struct._Range = type <{ i64, i64 }>
>>
>> define void @make_range(%struct._Range* noalias sret %agg.result...
2007 Jul 09
21
mthca use of dma_sync_single is bogus
...ingle contiguous or scatter/gather mapping. All the
parameters must be the same as those passed into the single mapping
API.
and mthca is *not* following this clear rule: it is trying to sync
only a subrange of the mapping. Later on in the document, there is:
void
dma_sync_single_range(struct device *dev, dma_addr_t dma_handle,
unsigned long offset, size_t size,
enum dma_data_direction direction)
does a partial sync. starting at offset and continuing for size. You
must be careful to observe the cache alignment and width when doing
anythi...