ons should take care of it, as they do in
others cases.
--
Krzysztof Halasa
\
> ^^ '0' means forcibly share an input
>operand with operand zero.
>
>> : "lr", "cc"); \
>> x = (u8) __r2; \
>> __e;\
>> })
>
> I think the macro could well be wrong. Do you know why those constraints
> were chosen?
No. The macro is in normal Linux ARM kernel.
--
Krzysztof Halasa
sl #1
50: e7c07008strbr7, [r0, r8]
54: 028a3001addeq r3, sl, #1 ; 0x1
58: 13ed mvnne r0, #13 ; 0xd
5c: 03a1moveq r0, #1 ; 0x1
60: 05883100streq r3, [r8, #256]
64: e89dadf0ldmia sp, {r4, r5, r6, r7, r8, sl, fp, sp, pc}
68: 0008andeq r0, r0, r8
Gcc bug? get_user() bug? Should I file a bug entry?
Gcc-4.1.2 and 4.1-CVS do a similar thing.
--
Krzysztof Halasa
f contract known to both parties at the time
of making the agreement.
--
Krzysztof Halasa
file it patches, so there's not much real meaning in talking
> about the license status of a patch in isolation.
I don't.
--
Krzysztof Halasa
GPLv2 (and any other licence).
--
Krzysztof Halasa
ss FSF agrees with Mark's proposal
> to dual license patches.)
I hope the COPYING or similar file will contain the licence text
under which the code is distributed?
--
Krzysztof Halasa
uot; clause).
Use any licence you want but don't mess with version numbers
or the branches (including closing) for purely political,
not technical reasons.
--
Krzysztof Halasa
printf("array: %i %i\n", array[0], array[1]);
test_it(array);
printf("array: %i %i\n", array[0], array[1]);
return 0;
}
--
Krzysztof Halasa
