Jim Huang

@yachiyang01, Please check the debugging messages generated by `chewing-editor -d` and look for related operations. We need to know more about program behavior.

@yachiyang01 , you should attach text messages as possible as you can since developers would like to figure out by searching certain words.

Good! Let's clarify the subject to be more precise. If key stroke sequence contains space which means vocal intensity in Bopomofo, `chewing-editor` would suffer from unexpected discard with phrases. @yachiyang01,...

@nickchen120235, I am writing another ebook about Linux CPU scheduler in which Ftrace was covered. I can send the draft for your reference. If you would like to contribute, please...

> The planned content is similar to [this](https://github.com/nickchen120235/linux-kernel-lab/tree/master/FINAL-system-call-hooking#method-2-ftrace-with-kprobe), of course the kprobe part will be omitted and the rest will be revised. It looks great. I like the sequence diagram...

Considered as complete.

[register usage histogram](https://gist.github.com/michaeljclark/8ba727e56084833e4f838c941eeca6be) generated by rv8.

Check the way how [mimalloc](https://github.com/microsoft/mimalloc) displays the internal information depending on environment variable `MIMALLOC_VERBOSE` and `MIMALLOC_SHOW_STATS`. Of course, the feature can be turned off via build-time flags.

It is feasible to reuse existing `map` for LRU cache implementation. See https://jaeyu.wordpress.com/2014/04/15/lru-cache-in-c/

> I imported the LRU cache in this [commit](https://github.com/qwe661234/rv32emu/commit/8da7364f968a930fa46e4a43af9f2e1820c420ad), The memory management concerns on basic block should appear in #105 . Here, we still work on the statistics.