Displaying 2 results from an estimated 2 matches for "ar_noalias".
2015 Jun 16
4
[LLVMdev] AliasAnalysis refactoring for the new pass manager
...Result { NoAlias, ... }" and update everywhere to
say explicitly "... != AliasResult::NoAlias".
3) Use "enum AliasResult { NoAlias = 0, ... }" and everything Just Works
but we pollute the llvm namespace with "NoAlias" and friends.
4) Use "enum AliasResult { AR_NoAlias = 0, ...}" to get the effect of #2
with some minimal name collision prevention.
Thoughts?
-Chandler
[1] Here is the completely untested sketch of what seems required:
https://ghostbin.com/paste/2bso6
On Mon, Jun 15, 2015 at 6:27 PM Daniel Berlin <dberlin at dberlin.org> wrote:
>...
2015 Jun 16
2
[LLVMdev] AliasAnalysis refactoring for the new pass manager
> On 2015-Jun-15, at 16:29, Chandler Carruth <chandlerc at gmail.com> wrote:
>
> On Mon, Jun 15, 2015 at 3:56 PM Duncan P. N. Exon Smith <dexonsmith at apple.com> wrote:
> I like this colour:
>
> enum class AliasKind /* or AliasCategory? */ {
> Null,
> Unknown,
> Partial,
> Complete
> };
>
> So, the only