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

The LLVM error code bug was resolved (#711)

Browse Source 
We already updated the other posts in https://github.com/phil-opp/blog_os/pull/644 but forgot to update this post
This commit is contained in:
Philipp Oppermann
2020-01-05 20:02:39 +01:00
committed by GitHub
parent 6db4e34c48
commit f1b13d7ed3
1 changed files with 0 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -193,12 +193,6 @@ In the `x86_64` crate, the interrupt stack frame is represented by the [`Interru
[`InterruptStackFrame`]: https://docs.rs/x86_64/0.8.1/x86_64/structures/idt/struct.InterruptStackFrame.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
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: