similar to: Clarifying pointer aliasing rules

Good evening to all. I find myself trying to create some Thiessen Polygons, in order to finish a meteorology research. This is the script I found to create the Polygons: * * *voronoipolygons <- function(x) {* * require(deldir)* * if (.hasSlot(x, 'coords')) {* * crds <- x@coords * * } else crds <- x* * z <- deldir(crds[,1], crds[,2])* * w <- tile.list(z)* * polys

My UPS is a Eaton Ellipse 1000S (But its identified as MGE Ellipse 0463:ffff). I have been using the usb interface with the usbhid-ups driver, but I found that sometimes (too much times) the driver doesn't respond and NUT doesn't receive changes nor notifications from the UPS. The kernel lose the connections with USB device, in the kernel logs appears: Dec 30 11:24:12 rei kernel:

On Thu, Oct 25, 2012 at 3:15 PM, Pranav Bhandarkar <pranavb at codeaurora.org>wrote: > Hi, > > I have the following IR code > > </snippet> > %prev = getelementptr inbounds %struct.myStruct* %node, i32 0, i32 1 > %1 = load %struct.myStruct** %prev, align 4, !tbaa !0 > %next1 = getelementptr inbounds %struct.myStruct* %1, i32 0, i32 0 > store %struct.myStruct*

On Thu, Oct 25, 2012 at 5:32 PM, Krzysztof Parzyszek < kparzysz at codeaurora.org> wrote: > On 10/25/2012 5:36 PM, Dan Gohman wrote: > >> >> First, yes, it is wrong for AliasAnalysis implementations to trust LLVM >> IR types, for the most part. There's nothing in LLVM IR which would >> prevent you from having two myStruct instances which overlap here,

Hi Ivan, On 2019-01-18 10:15, Ivan Kosarev wrote: > IIRC, there were proposals/attempts to represent accesses to array > elements as accesses to their first elements, which can technically be > encoded with the current TBAA format and thus may work as an > incremental improvement on top of the existing TBAA machinery you are > looking for. But this may need making sure there

On 10/25/2012 5:36 PM, Dan Gohman wrote: > > First, yes, it is wrong for AliasAnalysis implementations to trust LLVM > IR types, for the most part. There's nothing in LLVM IR which would > prevent you from having two myStruct instances which overlap here, > sharing 4 bytes. Because of that, next really could be equal to &prev. > > In theory, you could help this

Hi, I have the following IR code </snippet> %prev = getelementptr inbounds %struct.myStruct* %node, i32 0, i32 1 %1 = load %struct.myStruct** %prev, align 4, !tbaa !0 %next1 = getelementptr inbounds %struct.myStruct* %1, i32 0, i32 0 store %struct.myStruct* %0, %struct.myStruct** %next1, align 4, !tbaa !0 %2 = load %struct.myStruct** %prev, align 4, !tbaa ! </snippet> myStruct is

Hi, I'm not clear with the aliasing rules for the pointer pointing to const memory. It will be great help if someone clarify my doubts. Consider below test program: int foo(int *A, int *B, const int *C, int len) { for (int i = 0; i < len; i++) A[i] = B[i] + *C; } In this test case the type for "C" is const int * type, it means the pointer is pointing to a memory which is

On Wednesday 22 July 2009 13:30, Dan Gohman wrote: > - A pointer value formed by a ptrtoint is associated with all address > ranges of all pointer values that contribute (directly or > indirectly) to the computation of the pointer's value. Do you mean inttoptr here? And that "all pointer values that contribute (directly or indirectly) to the computation of the

Hi Ivan, > As to my own patches pending publication, they are all for the new > TBAA format, which you said would be of no help in your case. > I actually thought they would help, but merely suggested an intermediate step while waiting for those further improvements you are working on. I would be happy to try your patches and evaluate if it helps my test case... thanks /Jonas

On Jul 22, 2009, at 12:33 PM, David Greene wrote: > On Wednesday 22 July 2009 13:30, Dan Gohman wrote: > > >> - A pointer value formed by a ptrtoint is associated with all >> address >> >> ranges of all pointer values that contribute (directly or >> >> indirectly) to the computation of the pointer's value. >> > > Do you mean

Hi, Here's another case, different in high-level, but similar in low-level. When Fortran allocatable array is defined in module, its actual dimensions are kept in internal structure. Loads originated from reading these dimensions confuse Polly on any use of this array. Attachments: 1) Sample Fortran source code (to be compiled with and without -DMODULE to see failing and working version,

On Jul 22, 2008, at 2:51 PM, Stefanus Du Toit wrote: > On 22-Jul-08, at 1:22 PM, Dan Gohman wrote: >>> If I apply the patch found further down, LICM moves the loads out >>> (as >>> expected), but of course this is a fairly specific fix. >> >> Slightly better than checking for GlobalVariabls directly >> is to call the AliasAnalysis'

Hi, I found a difference between Clang and GCC in alias handling. This was with a benchmark where Clang was considerably slower, and in a hot function which does many more loads from the same address due to stores between the uses. In other words, a value is loaded and used, another value is stored, and then the first value is loaded once again before its second use. This happens many times,

Just one question for you all. Am I correct in assuming that Samba file permissions are linked to Linux? As in, I create a home directory called /home/user. The directory /home is shared. If I set the owner of the 'user' directory to the user called 'user', and changed the file permissions to 700, that would mean only 'user' and 'root' would be able to access

Just two clarifying questions about the package "pcse". Argument "groupN": It should be a factor that tells us to what subgroup each record belongs, right? Argument "groupT" should be a vector that contains the time identifier. Can it be just a factor (e.g., 1, 2, 3, etc.) - or does it have to be in the date format? Thank you very much! -- Dimitri Liakhovitski

Hi all, In the language specifications, many instructions have this form: <result> = ... So, where is "<result>" defined? Is it an integral part of an instruction? Consider the "getelementptr" instruction: <result> = getelementptr <pty>* <ptrval>{, <ty> <idx>}* How is the "<result>" represented? Best,

Yes, it's an integral part of the Instruction. You can change it by providing a name when you create the instruction. Reid On Thu, Jun 10, 2010 at 8:34 AM, Xiaolong Tang <xiaolong.snake at gmail.com> wrote: > Hi all, > > In the language specifications, many instructions have this form: > >  <result> = ... > > So, where is "<result>" defined?

On Feb 8, 2012, at 10:44 AM, James Molloy wrote: > Hi Owen, > > Having looked into this due to Clang failing PlumHall with it recently I can give an opinion... > > I think !NoExcessFPPrecision covers FMA completely. There are indeed some algorithms which give incorrect results when FMA is enabled, examples being those that do floating point comparisons such as: a * b + c - d. If

On Feb 8, 2012, at 10:42 AM, Hal Finkel wrote: > In my experience, users of numerical codes expect that the compiler will > use FMA instructions where it can, unless specifically asked to avoid > doing so by the user. Even though this can sometimes produce a different > result (*almost* always a better one), the performance gain is too large > to be ignored by default. I highly