search for: copyd

...to split this column into two columns (one with Data and one with the Time), the returned result is quite strange, as the two new columns appear to have more rows than the data frame: applicLog.dat <- read.delim("file.txt") #Process the syscreated column (Date time --> Date + time) copyDate <- applicLog.dat[["?..syscreated"]] copyDate <- as.character(copyDate) splitDate <- strsplit(copyDate, " ") splitDate <- unlist(splitDate) splitDateIndex <- c(1:length(splitDate)) sysCreatedDate <- splitDate[splitDateIndex %% 2 == 1] sysCreatedTime <- spl...

...doesn't actually define a value, it just moves it between locations. At least one optimisation (X86 LEAtoMOV) transforms instructions into COPYs (LEA $rsp + 0 => COPY $rsp), which is unfortunate. This doesn't happen a lot though, and can be fixed by dropping a DBG_PHI of the COPYd register nearby. Plus it only happens post-regalloc, which makes it less of a problem. * Trivial def rematerialization: there's no pattern to rely on in how the register allocator rematerializes values, and so values can rematerialize in different registers dominating different parts...

...y define a value, it just moves > it between locations. At least one optimisation (X86 LEAtoMOV) transforms > instructions into COPYs (LEA $rsp + 0 => COPY $rsp), which is unfortunate. > This doesn't happen a lot though, and can be fixed by dropping a DBG_PHI > of the COPYd register nearby. Plus it only happens post-regalloc, which > makes it less of a problem. > * Trivial def rematerialization: there's no pattern to rely on in how the > register allocator rematerializes values, and so values can rematerialize > in different registers dominat...