michaelkuc6/blog_os
1
0
Fork 0
mirror of https://github.com/phil-opp/blog_os.git synced 2025-12-16 14:27:49 +00:00
Code Issues Projects Releases Wiki Activity

Mention LLVM bug that leads to wrong error code

Browse Source 
See https://github.com/phil-opp/blog_os/issues/513
This commit is contained in:
Philipp Oppermann
2019-01-05 14:35:34 +01:00
parent ec377baa37
commit e9e4984643
1 changed files with 6 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
blog/content/second-edition/posts/06-cpu-exceptions/index.md
View File

@@ -190,6 +190,12 @@ In the `x86_64` crate, the exception stack frame is represented by the [`Excepti
[`ExceptionStackFrame`]: https://docs.rs/x86_64/0.2.8/x86_64/structures/idt/struct.ExceptionStackFrame.html [`ExceptionStackFrame`]: https://docs.rs/x86_64/0.2.8/x86_64/structures/idt/struct.ExceptionStackFrame.html
Note that there is currently [a bug in LLVM] that leads to wrong error code arguments. The cause of the issue is already known and a solution is [being worked on].
[a bug in LLVM]: https://github.com/rust-lang/rust/issues/57270
[being worked on]: https://reviews.llvm.org/D56275
### Behind the Scenes ### Behind the Scenes
The `x86-interrupt` calling convention is a powerful abstraction that hides almost all of the messy details of the exception handling process. However, sometimes it's useful to know what's happening behind the curtain. Here is a short overview of the things that the `x86-interrupt` calling convention takes care of: The `x86-interrupt` calling convention is a powerful abstraction that hides almost all of the messy details of the exception handling process. However, sometimes it's useful to know what's happening behind the curtain. Here is a short overview of the things that the `x86-interrupt` calling convention takes care of: