[PATCH] Allow to model non-affine control flow in a SCoP.
Johannes Doerfert
doerfert at cs.uni-saarland.de
Fri Feb 20 00:20:22 PST 2015
Codegen wasn't finished yesterday afternoon but it is now. I would have
commited it in two patches/reviews but I can merge them too if you'd
like.
On 02/20, Tobias Grosser wrote:
> On 19.02.2015 19:15, Johannes Doerfert wrote:
> >Hi grosser, sebpop, simbuerg, zinob,
> >
> > In order to model non-affine control flow SCoP statements can now
> > represent a basic block (precise/affine case) or a whole region
> > (non-affine case). In the latter all write accesses except the ones in
> > the region entry and exit will be may-write accesses as we cannot be
> > certain they are executed.
> >
> > As there is no real difference non-affine branches as well as floating
> > point branches are covered (and both called non-affine control flow).
> > Furthermore, conditionals as wells as loops with non-affine control
> > flow can be overapproximated.
> >
>
> I like the patch as well, but it seems to lack codegen support. Is this a
> proof-of-concept or is this intended to be committed as is?
>
> Tobias
--
Johannes Doerfert
Researcher / PhD Student
Compiler Design Lab (Prof. Hack)
Saarland University, Computer Science
Building E1.3, Room 4.31
Tel. +49 (0)681 302-57521 : doerfert at cs.uni-saarland.de
Fax. +49 (0)681 302-3065 : http://www.cdl.uni-saarland.de/people/doerfert
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 213 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20150220/8fe6f1de/attachment.sig>
More information about the llvm-commits
mailing list