similar to: [LLVMdev] BasicAA unable to analyze recursive PHI nodes

Sorry for missing this the first time around, but I think -scev-aa does what you want. I've commented on the phabricator review. On Wed, Jun 10, 2015 at 3:32 PM, Tobias Edler von Koch <tobias at codeaurora.org> wrote: > On Tue, 2 Jun 2015 11:32:13 -0500 Tobias Edler von Koch > <tobias at codeaurora.org> wrote: > >> Hi all, >> >> I came across the

On Wed, Jun 10, 2015 at 4:09 PM, Tobias Edler von Koch <tobias at codeaurora.org> wrote: > It probably will, but it isn't on by default (right?) True, but so what? > and has quite a > lot more overhead. I didn't see numbers one way or the other. It probably has some overhead, if it's the right solution, i'm sure it can be ade faster. > I think this is a common

> Not a huge change here although the numbers tend to be more on the side > of a slowdown. This is interesting - you'd think that better alias > analysis shouldn't have that effect. Any idea what could be causing > this? LLVM's alias analysis is good but not amazing. If you improve it significantly (as you appear to have :P), you give the compiler more freedom to do

----- Original Message ----- > From: "Tobias Edler von Koch" <tobias at codeaurora.org> > To: "Daniel Berlin" <dberlin at dberlin.org> > Cc: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> > Sent: Thursday, June 11, 2015 10:02:37 AM > Subject: Re: [LLVMdev] BasicAA unable to analyze recursive PHI nodes > > Hi Daniel,

Am Di., 17. März 2020 um 16:56 Uhr schrieb Chawla, Pankaj via llvm-dev <llvm-dev at lists.llvm.org>: > All I am expecting from DA is a direction vector containing (*). There seems to be a bug in DI, see Felipe's answer. > I think the main problem is that currently there is no exact way DA can query AliasAnalysis in a ‘conservatively correct’ manner. > > Using UnknownSize

As far Am Mi., 18. März 2020 um 11:34 Uhr schrieb Chawla, Pankaj <pankaj.chawla at intel.com>: > >> There seems to be a bug in DI, see Felipe's answer. > Maybe I missed something. There seems to be no resolution to the problem. How can DA fix this without help from alias analysis? DependenceInfo is not using the AA interface correctly. Either DI has to be fixed, or another

My understanding is that alias analysis returns results in the function scope, not in loop scope. Since both the phis access both global arrays, that should results in BasicAA conservatively returning MayAlias. I debugged this a little bit and narrowed it down to the section of the code in BasicAAResult::aliasPHI() which has this comment- // Analyse the PHIs' inputs under the assumption

AliasAnalysis and dependence analysis answer different problems. AA check whether two memory ranges accessed at the same time (i.e. in the same iteration) do not overlap. DI checks when two accesses, not necessarily executed in the same iteration, do overlap. DI makes use of AA in verifying that the base pointer (with unknown size), at the beginning of the loop, themselves do not overlap. If they

Hi Hal, In that case what is the best way to query whether there is a loop carried dependence between B[j] and A[j] at i-loop level? We were operating under the assumption of 'conservatively correct' behavior of alias analysis in the function scope? Thanks, Pankaj From: Finkel, Hal J. <hfinkel at anl.gov> Sent: Tuesday, March 17, 2020 11:50 AM To: Hiroshi Yamauchi <yamauchi at

Hi all, I have this test case- #define N 1000 extern double Ag[N]; extern double Bg[N]; void consume(double *A, double *B); void swap_deps() { double *A = Ag; double *B = Bg; for (int i = 0; i < 97; ++i) { for (int j = 0; j < N; ++j) { B[j] = A[j] + 1; } double *tmp = A; A = B; B = tmp; } consume(A, B); } BasicAA is returning 'NoAlias' when

Hello, A few months ago the distribution I use (Debian Testing) moved from Samba 3 to Samba 4 - I started seeing a lot of problems. Since then there are two bugs I find occurring on a regular basis: 1. Consistent dumping core on a regular basis (very rarely, if ever occurred with Samba 3) a. $ ls -ltr *core*smbd* |wc -l b. 1297 c. $ du -ach *core*smbd*|tail -n 1

Am Mi., 18. März 2020 um 18:15 Uhr schrieb Chawla, Pankaj <pankaj.chawla at intel.com>: > > >> DependenceInfo is not using the AA interface correctly. Either DI has to be fixed, or another method added to AA that gives additional guarantees. Please see the bug report for details. > > Thanks for updating the bug report but GetUnderlyingObject() doesn't help in this case.

Alias analysis is figuring out the relationship between two pointer expressions, at some location in the program. At a given point in the program, do two expressions always refer to the same location? At a given point in the program, do two expressions never refer to the same location? AliasAnalysis::alias() doesn't explicitly take a "point" in the program because we don't

Hello, i have ported the BCP (Bride Control Protocol) patch for pppd 2.4.1 mentioned in http://lists.osdl.org/pipermail/bridge/2004-September/000619.html to pppd 2.4.2. The kernel patch still works without problems with kernel 2.4.30. Perhaps someone else could use this patch ... Here again some documentation i have found about the BCP patch somewere else: When pppd negotiates BCP, it tells

In general I use DebugInfoFinder and clear out Metadata if GV in null or GV->isDeclaration(). If there is any interest, I can post that patch... Sergei --- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation > -----Original Message----- > From: Tobias Edler von Koch [mailto:tobias at codeaurora.org] > Sent: Friday, February 12, 2016

Hello, In the "Documentos" section SanJaaC Electronics' website you can now find a zipped version of the paper "The use of multirate filter banks for coding of high quality digital audio" by T. Sporer, K. Brandenburg and B. Edler. I hope this helps to relieve the shortcoming with the -404 error message when trying to access it form other sites. Please let me know if I am

It seems the same bug is there if we do pointer swapping with selects. Do you agree? (see example below) define void @f() { entry: %a1 = alloca float, align 4 %a2 = alloca float, align 4 br label %loop end: ret void loop: %phi = phi i32 [ 0, %entry ], [ 1, %loop ] %select_cond = icmp eq i32 %phi, 0 %ptr1 = select i1 %select_cond, float* %a1, float* %a2 %ptr2 = select i1

Oh. So it wasn't just the memory location size that was incorrect on those aliasing checks. I took a look at the tests and it appears that the alias call also catches some cases of restrict/noalias attributes, along with the tbaa info. My first idea of constructing an alias call with no Ptr's but valid tbaa info won't catch that at least. I will create a bug report and try and see if

FYI, The LLVM Performance Workshop will be held at CGO 2017. The workshop is co-located with CC, HPCA, and PPoPP. If you are interested in attending the workshop, please register at the CGO website: http://cgo.org/cgo2017/workshops.html When: Saturday February 4th, 2017 Where: Austin, Texas, USA ---- Hi, CGO workshop and tutorial organizers, This is a friendly reminder that early

Dear Sir, I was trying to install bridge as we are installing scps gateway in our testbed.This requires us to install the bridge. Our Linux version is 2.4.18 ~3 and we are using redhat 7.2 Please let me know which is the bridge I should install and how to configure it. Before configuring the bridge what I should check in my configuration. Thanks for your time, Sincerely Rama ===== I hear