[Bug target/101276] [i386] Keylocker output should be cleared when instruction reports runtime error.

[wwwhhhyyy333 at gmail dot com via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101276

Hongyu Wang  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #4 from Hongyu Wang  ---
Fixed by
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=1aeefa5720a71e622e2f26bf10ec8e7ecbd76f4c

[Bug target/101276] [i386] Keylocker output should be cleared when instruction reports runtime error.

[crazylht at gmail dot com via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101276

--- Comment #3 from Hongtao.liu  ---
(In reply to Richard Biener from comment #2)
> It might slow down things when data is encrypted in a loop and the error
> state
> is accumulated and checked afterwards?

This is the exact case that the user mentioned, by the time the state is
checked, idata has been already written to odata. They hope when intructions
failed to encrpt idata, 0 would used for odata.

[Bug target/101276] [i386] Keylocker output should be cleared when instruction reports runtime error.

[rguenth at gcc dot gnu.org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101276

--- Comment #2 from Richard Biener  ---
It might slow down things when data is encrypted in a loop and the error state
is accumulated and checked afterwards?

Maybe warrants a -msecured-kl option or so?

[Bug target/101276] [i386] Keylocker output should be cleared when instruction reports runtime error.

[crazylht at gmail dot com via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101276

Hongtao.liu  changed:

   What|Removed |Added

 CC||crazylht at gmail dot com

--- Comment #1 from Hongtao.liu  ---
Note this is not a bug, but a re-implementation of the keylocker intrinsic from
a security perspective.