Displaying 3 results from an estimated 3 matches for "globalmapping".
2019 Sep 27
3
DenseMap/ValueMap: is M[New]=M[Old] valid ?
On Thu, 26 Sep 2019, David Blaikie wrote:
> I'd be surprised if Clang or GCC's behavior here varied depending on the
> size of anything, but maybe?
>
> In any case, C++17 or so requires the RHS to be evaluated before the LHS for
> assignments - so this is now /always/ wrong, not just unspecified (which, I
> guess, also always wrong... just sometimes accidentally right)
2019 Sep 27
2
DenseMap/ValueMap: is M[New]=M[Old] valid ?
I actually ran into an elusive bug with this exact same issue some time
ago as well, see https://bugs.llvm.org/show_bug.cgi?id=42065 and
https://reviews.llvm.org/D62624.
The strange thing about that bug was that it only showed up if built with
GCC; Clang dereferenced the right hand side reference before evaluating
the left hand side, as long as the value type was as small as the
reference
2013 Apr 04
0
[LLVMdev] ExecutionEngine::updateGlobalMapping
Hello,
I am using updateGlobalMapping to inform the JIT engine the address of some C helpers. Due to the nature of the analysis pass, there can be several calls to updateGlobalMapping with the same GlobalValue key and the same (or sometimes different) address.
My problem is when the reverse mapping is enabled, the following fragment:...