Displaying 3 results from an estimated 3 matches for "bit3".
Did you mean:
bit
2009 Feb 24
4
[PATCH]xend: fix a typo in pci.py
The PCI_EXP_TYPE_PCI_BRIDGE should be PCI_EXP_FLAGS_TYPE here.
Also a tiny fix to the python comment.
Signed-off-by: Dexuan Cui <dexuan.cui@intel.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
2019 Jun 17
2
[InstCombine] addrspacecast assumed associative with gep
...s with much in LLVM), however this removes the opportunity for globally allocating low cost atomic flags.
Modelled as address spaces, p0 and p<bit> would have different CHAR_BITs, of 8 and 1 respectively. This somewhat works as one would expect too, with, ((bit *)&somevalue)[3] producing bit3 of somevalue - at least until the first time you access through a struct or array:
gep(addrspacecast(gep p0, 4) to p<bit>, 3) == (p0 + 4) * 8 + 3
As LLVM optimises this expression to:
addrspacecast(gep p0, 4 + 3) to p<bit>
Producing something entirely different.
But that said, I...
2019 Jun 11
3
[InstCombine] addrspacecast assumed associative with gep
The following combine(-enabling transformation) makes me
uncomfortable:
gep(addrspacecast(gep p0) to p1)
addrspacecast(gep(gep p0)) to p1
It's applied at visitAddrSpaceCast in InstCombineCasts.cpp.
Before this, I'd always assumed address spaces were very much "user
domain". Datalayout even supports marking a space as "non-integral",
to designate that manipulation as