Displaying 3 results from an estimated 3 matches for "xbegin".
Did you mean:
begin
2013 Apr 30
1
Trabajar con un argumento opcional como escalar o vector.
...el argumento opcional debería poder ser escalar o vector.
Necesito definir una función 'aplicaratodasfilas' que llama a otra función 'atomica' que no admite vectores y que requiere también argumentos opcionales.
Pongo un ejemplo:
# Se aplica a cada fila.
atomica <- function(xbegin, xend, npoints = 5, ...) { # los argumentos opcionales ... son necesarios ya que hay más funciones dentro
seq(xbegin,xend,length.out = npoints) # la función seq no admite vectores
}
aplicaratodaslasfilas <- function(data, ...) {
lapply(1:dim(data)[1], function(i,...) {
atomica(xbegin=d...
2014 May 29
3
[LLVMdev] Proposal: "load linked" and "store conditional" atomic instructions
...br i1 %success, label %end, label %loop
end:
ret void
}
That kind of analysis is a very big burden to put on any pass. On the
other hand, mapping the other way doesn't seem much simpler either.
I feel like there ought to be a good way to combine this with
Haswell's xbegin/xend functionality in an even more generic IR
construct too, but I can't quite come up with a representation. More
thought needed.
> Tim, for those of us not directly involved, could you share a selection of
> bugs or other background? I'd like to read through and try to get a bette...
2014 May 29
4
[LLVMdev] Proposal: "load linked" and "store conditional" atomic instructions
Hi,
I've been looking at improving atomicrmw & cmpxchg code more,
particularly on architectures using the load-linked/store-conditional
model.
The summary is that current expansion for cmpxchg seems to happen too
late for LLVM to make meaningful use of the opportunities it provides.
I'd like to move it earlier and express it in terms of a first-class
pair of "load linked"