Displaying 2 results from an estimated 2 matches for "0x1234abcd".
2018 Oct 06
1
TLS handshake failure - Client Helo rejected
...onnecting to [XXXXXX.XXX:143, tlsStrict, login = 0, pass = true, cert = false]
2018.09.15 23:27:57.274 +0200 [NETWRK.2652] Resolving address for XXXXXX.XXX
2018.09.15 23:27:57.280 +0200 [CONCTR.1] Service state change: uri: content://org.kman.AquaMail.data/accounts/2/out/231588601, what: 160, aux = 0x1234abcd
2018.09.15 23:27:57.281 +0200 AccountListShard Send state: uri: content://org.kman.AquaMail.data/accounts/2/out/231588601, what: 160, aux = 0x1234abcd
2018.09.15 23:27:57.281 +0200 [CONCTR.1] Service state change: uri: content://org.kman.AquaMail.data/accounts/2/out/231588601, what: 160, aux = 0x12...
2011 Jul 16
2
[LLVMdev] [RFC] LegalizeDAG support for targets without subword load/store instructions
...*****
r6 = 0xABCD #s2 value doesn't need to be shifted
r7 = r5 & 0xFFFF0000 #Mask out s2 bits
r8 = r7 | r6 #OR in s2 value
mem[(0x1002 & ~0x3)] = r8 #Store back word containing new s2 value
If all goes well, the word at mem[0x1000] should read 0x1234ABCD after
we're done.
NOTE: The two starred instructions (the store for s1 and the load for
s2) *must* be executed in that order. Otherwise, the s2
read-modify-write will see the old value of s1, and will clobber it when
it writes back (yielding an incorrect mem[0x1000] value of 0x0000ABCD)....