Displaying 4 results from an estimated 4 matches for "checkint".
Did you mean:
checking
2015 Apr 26
7
[Bug 2390] New: PROTOCOL.key mis-describes private section
...org
Reporter: anakin at pobox.com
Created attachment 2607
--> https://bugzilla.mindrot.org/attachment.cgi?id=2607&action=edit
test key file
The file openssh/PROTOCOL.key documents the (optionally) encrypted
section of a new-format private key file as containing
uint32 checkint
uint32 checkint
string privatekey1
string comment1
...
Therefore, I expect each private key to be wrapped in a single large
SSH-2 "string", inside which I expect a second layer of data
marshalling such as the key type string and various mpints.
However...
2016 Dec 14
2
LLD status update and performance chart
...:relocateOne in tools/lld/ELF/Target.cpp has this:
switch (Type) {
case R_PPC64_ADDR14: {
checkAlignment<4>(Val, Type);
// Preserve the AA/LK bits in the branch instruction
uint8_t AALK = Loc[3];
write16be(Loc + 2, (AALK & 3) | (Val & 0xfffc));
break;
}
case R_PPC64_ADDR16:
checkInt<16>(Val, Type);
write16be(Loc, Val);
break;
case R_PPC64_ADDR16_DS:
checkInt<16>(Val, Type);
write16be(Loc, (read16be(Loc) & 3) | (Val & ~3));
break;
... (and so on; there are obviously lots of relocation types)
void RuntimeDyldELF::resolvePPC64Relocation in lib/Executi...
2016 Dec 14
0
LLD status update and performance chart
...{
> case R_PPC64_ADDR14: {
> checkAlignment<4>(Val, Type);
> // Preserve the AA/LK bits in the branch instruction
> uint8_t AALK = Loc[3];
> write16be(Loc + 2, (AALK & 3) | (Val & 0xfffc));
> break;
> }
> case R_PPC64_ADDR16:
> checkInt<16>(Val, Type);
> write16be(Loc, Val);
> break;
> case R_PPC64_ADDR16_DS:
> checkInt<16>(Val, Type);
> write16be(Loc, (read16be(Loc) & 3) | (Val & ~3));
> break;
> ... (and so on; there are obviously lots of relocation types)
>
>...
2016 Dec 14
0
LLD status update and performance chart
On Tue, Dec 13, 2016 at 12:08 PM, Rui Ueyama <ruiu at google.com> wrote:
> On Tue, Dec 13, 2016 at 12:01 PM, Mehdi Amini <mehdi.amini at apple.com>
> wrote:
>
>>
>> On Dec 13, 2016, at 11:51 AM, Rui Ueyama <ruiu at google.com> wrote:
>>
>> On Tue, Dec 13, 2016 at 11:37 AM, Mehdi Amini <mehdi.amini at apple.com>
>> wrote:
>>