llvm-D50010-VNCoercion-ni
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Mon, 20 Jan 2020 09:26:04 +0000 (09:26 +0000)
committerGianfranco Costamagna <locutusofborg@debian.org>
Mon, 20 Jan 2020 09:26:04 +0000 (09:26 +0000)
commitc95acc470f17e6a591fe24365e20c2f7716ac5a8
treecddf3df77256b83fee7b5dcec8ac792e1700d3fb
parent3e981f1cd1649930aed84035ecd8843f77606b1b
llvm-D50010-VNCoercion-ni

commit 8eb2b102a203d83fb713f3bf79acf235dabdd8cd
Author: Keno Fischer <keno@juliacomputing.com>
Date:   Mon Jul 30 16:59:08 2018 -0400

    [VNCoercion] Disallow coercion between different ni addrspaces

    Summary:
    I'm not sure if it would be legal by the IR reference to introduce
    an addrspacecast here, since the IR reference is a bit vague on
    the exact semantics, but at least for our usage of it (and I
    suspect for many other's usage) it is not. For us, addrspacecasts
    between non-integral address spaces carry frontend information that the
    optimizer cannot deduce afterwards in a generic way (though we
    have frontend specific passes in our pipline that do propagate
    these). In any case, I'm sure nobody is using it this way at
    the moment, since it would have introduced inttoptrs, which
    are definitely illegal.

    Fixes PR38375

    Reviewers: sanjoy, reames, dberlin

    Subscribers: llvm-commits

    Differential Revision: https://reviews.llvm.org/D50010

Gbp-Pq: Topic julia
Gbp-Pq: Name llvm-D50010-VNCoercion-ni.patch
lib/Transforms/Utils/VNCoercion.cpp
test/Transforms/GVN/non-integral-pointers.ll