similar to: [LLVMdev] How to get ELF section virtual starting address from MCSymbolRefExpr?

2011/11/19 Tobias Grosser <tobias at grosser.es>: > On 11/18/2011 01:34 PM, Marcello Maggioni wrote: >> >> Ok , this is what I believe is the final patch that adds the >> non-affine accept functionality to Polly, this should have no issues. >> >> I added three tests, two in ScopInfo (two simple tests, one expected >> fail and one success based on the

On 11/18/2011 01:34 PM, Marcello Maggioni wrote: > Ok , this is what I believe is the final patch that adds the > non-affine accept functionality to Polly, this should have no issues. > > I added three tests, two in ScopInfo (two simple tests, one expected > fail and one success based on the same source) and one in CodeGen that > verifies that the code is generated. > > The

2011/11/14 Tobias Grosser <tobias at grosser.es>: > On 11/14/2011 01:24 AM, Marcello Maggioni wrote: >> >> Hi Tobias. >> >> I worked on enabling Polly accepting non affine memory accesses and I >> produced a patch. > > Great. > >> I saw that there were a lot of updates in Polly recently, so I had to >> redo a lot of the work I did and

On 11/14/2011 01:24 AM, Marcello Maggioni wrote: > Hi Tobias. > > I worked on enabling Polly accepting non affine memory accesses and I > produced a patch. Great. > I saw that there were a lot of updates in Polly recently, so I had to > redo a lot of the work I did and that slowed me quite a bit. Ups, sorry! However, I believe without these changes detecting non-affine memory

2011/11/15 Marcello Maggioni <hayarms at gmail.com>: > 2011/11/14 Tobias Grosser <tobias at grosser.es>: >> On 11/14/2011 02:45 PM, Marcello Maggioni wrote: >>> >>> 2011/11/14 Tobias Grosser<tobias at grosser.es>: >>>> >>>> On 11/14/2011 01:24 AM, Marcello Maggioni wrote: >>>>> >>>>> Hi Tobias.

2011/11/18 Marcello Maggioni <hayarms at gmail.com>: > 2011/11/15 Marcello Maggioni <hayarms at gmail.com>: >> 2011/11/14 Tobias Grosser <tobias at grosser.es>: >>> On 11/14/2011 02:45 PM, Marcello Maggioni wrote: >>>> >>>> 2011/11/14 Tobias Grosser<tobias at grosser.es>: >>>>> >>>>> On 11/14/2011 01:24

2011/11/14 Tobias Grosser <tobias at grosser.es>: > On 11/14/2011 02:45 PM, Marcello Maggioni wrote: >> >> 2011/11/14 Tobias Grosser<tobias at grosser.es>: >>> >>> On 11/14/2011 01:24 AM, Marcello Maggioni wrote: >>>> >>>> Hi Tobias. >>>> >>>> I worked on enabling Polly accepting non affine memory accesses

On Nov 19, 2011 7:45 PM, "Tobias Grosser" <tobias at grosser.es> wrote: > > On 11/19/2011 10:43 AM, Bernhard Reutner-Fischer wrote: >> >> >> On Nov 19, 2011 5:40 PM, "Tobias Grosser" <tobias at grosser.es >> <mailto:tobias at grosser.es>> wrote: >> > >> > On 11/18/2011 01:34 PM, Marcello Maggioni wrote:

On 11/14/2011 02:45 PM, Marcello Maggioni wrote: > 2011/11/14 Tobias Grosser<tobias at grosser.es>: >> On 11/14/2011 01:24 AM, Marcello Maggioni wrote: >>> >>> Hi Tobias. >>> >>> I worked on enabling Polly accepting non affine memory accesses and I >>> produced a patch. >> >> Great. >> >>> I saw that there were

On 11/19/2011 10:43 AM, Bernhard Reutner-Fischer wrote: > > On Nov 19, 2011 5:40 PM, "Tobias Grosser" <tobias at grosser.es > <mailto:tobias at grosser.es>> wrote: > > > > On 11/18/2011 01:34 PM, Marcello Maggioni wrote: > > > > + // Devide the access function by the size of the elements in > the array. > > Decide, with a

Mmm I found out a very strange behavior (to me) of the SCEV analysis of the loop bound of the external loop I posted. When in ScopDetection it gets the SCEV of the external loop bound in the "isValidLoop()" function with: const SCEV *LoopCount = SE->getBackedgeTakenCount(L); It returns a SCEVCouldNotCompute, but if I change the "if" block inside the loop from: if

So, an update. I have managed to generate comments, although it does create a non-existent instruction. My method is as follows (and I would appreciate any comments on how to do it "better", although note that this won't make it into the final code :).) 1. I declared a "fake" instruction type to hold comments, ala: class FakeInst<dag outs, dag ins, string asmstr,

On Nov 19, 2011 5:40 PM, "Tobias Grosser" <tobias at grosser.es> wrote: > > On 11/18/2011 01:34 PM, Marcello Maggioni wrote: > > + // Devide the access function by the size of the elements in the array. Decide, with a 'c', please. Multiple other occurances below, too. Thanks, -------------- next part -------------- An HTML attachment was scrubbed... URL:

Dear all, I am looking to output assembly comments in my emitPrologue() function, just for my own readability. Searching for a way to do this found me this thread - http://lists.cs.uiuc.edu/pipermail/llvmdev/2011-October/043722.html, which says that the best way to output comments from somewhere like emitPrologue() is to: 1. Create an MDString for the comment. 2. Attach it to an LLVM

Sorry for the noobish question, but what kind of subscripts generate a SCEVCouldNotCompute from the SCEV engine? I tried for a while but I wasn't able to trigger that. 2011/11/20 Tobias Grosser <tobias at grosser.es>: > On 11/20/2011 03:01 AM, Marcello Maggioni wrote: >> >> 2011/11/19 Tobias Grosser<tobias at grosser.es>: >>> >>> On 11/18/2011

Hi, I'd like to ask another thing about Polly and SCoP discarding. I've noticed that Polly discards quite simple loops like: for (int i = 1; i < 1000; i++) {} or for (int i= 0; i < 1000; i+=2) {} is this an intended behavior or there is some way to make it accept these kind of loops ? Thanks, Marcello 2011/10/3 Marcello Maggioni <hayarms at gmail.com>: > Hi Tobias,

On 11/20/2011 03:01 AM, Marcello Maggioni wrote: > 2011/11/19 Tobias Grosser<tobias at grosser.es>: >> On 11/18/2011 01:34 PM, Marcello Maggioni wrote: >>> >>> Ok , this is what I believe is the final patch that adds the >>> non-affine accept functionality to Polly, this should have no issues. >>> >>> I added three tests, two in ScopInfo

2012/2/12 Tobias Grosser <tobias at grosser.es>: > On 02/08/2012 08:08 PM, Marcello Maggioni wrote: >> >> Hi, I'm using Polly to analyze memory access patterns for an >> university project and I'm trying to get polly working on some loops >> that polly marks as "containing non affine branches" . > > > Hi Marcello, > > sorry for the

Star Tan wrote: > I have found that the extremely expensive compile-time overhead comes from the string buffer operation for "INVALID" MACRO in the polly-detect pass. > Attached is a hack patch file that simply remove the string buffer operation. This patch file can significantly reduce compile-time overhead when compiling big source code. For example, for oggen*8.ll, the compile

Hi Tobias, thanks for the answer. I'll try to give a look to the code you pointed me to , and I'll try to make the modification myself. I'm new to LLVM and Polly, but the code of both seem clean and understandable, so I hope to be able to do it myself. In case I'll ask here for support :) Marcello 2011/10/1 Tobias Grosser <tobias at grosser.es>: > On 10/01/2011 03:26