search for: d68484

...#39; [2] Any help with extra testing and code review is welcome. To be generally useful, there are also some small gaps [1] that need to be filled: IR bitcode support and the new pass manager support. Any help with those is also welcome ! Thanks, Jeroen Dobbelaere [1] https://reviews.llvm.org/D68484 [2] https://lists.llvm.org/pipermail/llvm-dev/2019-March/131127.html

...Metadata operands where each partition is an ordered set of Metadata operands belonging to a specific domain. * Proposal #2: (Related to Issue #3) Design a hierarchical representation for the metadata operands in Alias.Scope and NoAlias sets. * Proposal #3: https://reviews.llvm.org/D68484 provides the infrastructure to fix issue #4. It might also help with issue #1 and issue #3 as it makes it possible to share scopes. Notes * Tarique presented challenges with the current prototype, including that there’s currently no way to differentiate noalias MD from other kinds of metada...

...est that came up during the round table, is to split up the documentation in two parts: a separate document describing the noalias architecture, and the LangRef, describing the intrinsics. I'll be working on that in the coming days. Thanks, Jeroen Dobbelaere [1] https://reviews.llvm.org/D68484 [PATCH 01/38] [noalias] LangRef: noalias intrinsics and noalias_sidechannel documentation. [2] https://reviews.llvm.org/D69542 Full Restrict Support - single patch

...ed as different types. Any idea what the best way is to handle (or fix) this ? (My feeling is that the name mangling should be improved, but at the moment I have no clue what the right approach would be) Thanks, Jeroen Dobbelaere [0] The problem, as reported by Nikita: https://reviews.llvm.org/D68484#2372356 [1] Intrinsic::getName https://github.com/llvm/llvm-project/blob/master/llvm/lib/IR/Function.cpp#L775 [2] getMangledTypeStr for a struct: https://github.com/llvm/llvm-project/blob/master/llvm/lib/IR/Function.cpp#L725 [3] The actual intrinsic creation that triggered the problem: https://re...

Hi, We, IBM XL Fortran compiler team, is interested in representing Fortran alias information in LLVM IR. We use the XL Fortran frontend to emit LLVM IR that includes alias information to feed to the LLVM in order to create object files. For the Fortran alias representation in LLVM IR, we considered both TBAA and ScopeAlias/NoAlias metadata approaches, we think that the ScopeAlias/NoAlias

Hi, Looking at how noalias is defined: https://llvm.org/docs/LangRef.html#noalias-and-alias-scope-metadata "When evaluating an aliasing query, **if for some domain**, the set of scopes with that domain in one instruction’s alias.scope list is a subset of (or equal to) the set of scopes for that domain in another instruction’s noalias list, then the two memory accesses are assumed not to

I'm having an issue where SROA will throw away no-alias information on some loads after inlining, because the loads are derived from a store to an alloca which can be removed after inlining. The pointers that were originally stored into the alloca do *not *have any aliasing information - the only context that allowed me to assert aliasing was that the inlined-function guaranteed it to be so.

To join our call on Thursday, May 28th @ 9-10 AM central time / 2-3 PM UTC please use this information: Meeting URL https://bluejeans.com/643493129?src=join_info Meeting ID 643 493 129 Want to dial in from a phone? Dial one of the following numbers: +1.312.216.0325 (US (Chicago)) +1.408.740.7256 (US (San Jose)) +1.866.226.4650 (US Toll Free) (see all numbers -