search for: countephemerals

...ion. This may not be important for debug intrinsics, but certainly is for features intended to help optimization. Based on this, it seems that we need to differentiate two classes of users: real users and, as Chandler called them, ephemeral users. We could update hasOneUser() to be hasOneUser(bool countEphemerals = false), or something like that, and the trick will be to support this without requiring additional iteration over all users. Thoughts? We should also use this new class of users to replace a lot of the special-case code that currently exists for making some of these intrinsics free (and removing...

...may not be important for debug intrinsics, but certainly is for features intended to help optimization. > > Based on this, it seems that we need to differentiate two classes of users: real users and, as Chandler called them, ephemeral users. We could update hasOneUser() to be hasOneUser(bool countEphemerals = false), or something like that, and the trick will be to support this without requiring additional iteration over all users. Thoughts? Redefining hasOneUser() would be the most efficient approach, and definitely possible. But it would add complexity to a fundamental property of the IR and potent...

...tainly is for > > features intended to help optimization. > > > > Based on this, it seems that we need to differentiate two classes > > of users: real users and, as Chandler called them, ephemeral > > users. We could update hasOneUser() to be hasOneUser(bool > > countEphemerals = false), or something like that, and the trick > > will be to support this without requiring additional iteration > > over all users. Thoughts? > > Redefining hasOneUser() would be the most efficient approach, and > definitely possible. But it would add complexity to a fundam...

...for debug intrinsics, but certainly is for > features intended to help optimization. > > Based on this, it seems that we need to differentiate two classes > of users: real users and, as Chandler called them, ephemeral > users. We could update hasOneUser() to be hasOneUser(bool > countEphemerals = false), or something like that, and the trick > will be to support this without requiring additional iteration > over all users. Thoughts? > > Redefining hasOneUser() would be the most efficient approach, and > definitely possible. But it would add complexity to a fundamental >...

On Feb 7, 2013, at 10:58 PM, Hal Finkel <hfinkel at anl.gov> wrote: >> As long as this is brainstorming time, I actually like the idea of an >> llvm.invariant intrinsic that the optimizers know to ignore. I like >> it for other purposes, but would happen to work for you as a >> temporary workaround. It could take one or two IR values (as >> metadata operands)

...ut certainly is for >> features intended to help optimization. >> >> Based on this, it seems that we need to differentiate two classes >> of users: real users and, as Chandler called them, ephemeral >> users. We could update hasOneUser() to be hasOneUser(bool >> countEphemerals = false), or something like that, and the trick >> will be to support this without requiring additional iteration >> over all users. Thoughts? >> >> Redefining hasOneUser() would be the most efficient approach, and >> definitely possible. But it would add complexity t...

...>> features intended to help optimization. >>> >>> Based on this, it seems that we need to differentiate two classes >>> of users: real users and, as Chandler called them, ephemeral >>> users. We could update hasOneUser() to be hasOneUser(bool >>> countEphemerals = false), or something like that, and the trick >>> will be to support this without requiring additional iteration >>> over all users. Thoughts? >> >> Redefining hasOneUser() would be the most efficient approach, and >> definitely possible. But it would add comp...

----- Original Message ----- > From: "Andrew Trick" <atrick at apple.com> > To: "Michele Scandale" <michele.scandale at gmail.com> > Cc: "llvmdev at cs.uiuc.edu List" <llvmdev at cs.uiuc.edu> > Sent: Thursday, February 7, 2013 11:56:42 PM > Subject: Re: [LLVMdev] Rotated loop identification > > > On Feb 7, 2013, at 10:53 AM,

...for debug intrinsics, but certainly is for > features intended to help optimization. > > Based on this, it seems that we need to differentiate two classes > of users: real users and, as Chandler called them, ephemeral > users. We could update hasOneUser() to be hasOneUser(bool > countEphemerals = false), or something like that, and the trick > will be to support this without requiring additional iteration > over all users. Thoughts? > > Redefining hasOneUser() would be the most efficient approach, and > definitely possible. But it would add complexity to a fundamental >...