Rework of f4d57f9b710de20c7cf04c8ab07e3af7c577a5c1

[kkebo]

Rework of f4d57f9 is needed.

Originally posted by @kkebo in #34 (comment)

[kkebo]

I tried to:

• remove @_optimize(none) from Framebuffer.init()
  • Real device: not work
  • QEMU: work
• change from @_optimize(none) to @inline(never)
  • Real device: not work
  • QEMU: work
• use Framebuffer(...) instead of Framebuffer.shared in kmain()
  • Real device: not work work
  • QEMU: work
• remove @_optimize(none) from Framebuffer.init(), and use Framebuffer(...) instead of Framebuffer.shared in kmain()
  • QEMU: not work
• change from @_optimize(none) to @inline(never), and use Framebuffer(...) instead of Framebuffer.shared in kmain()
  • QEMU: not work
• remove -Xswiftc -Osize --experimental-lto-mode=full -Xswiftc -experimental-hermetic-seal-at-link from swift build
  • Real device: not work
  • QEMU: work
• remove @_optimize(none) from Framebuffer.init(), use Framebuffer(...) instead of Framebuffer.shared in kmain(), and remove all arguments from Framebuffer.init()
  • Real device: work
  • QEMU: work

[kkebo]

use Framebuffer(...) instead of Framebuffer.shared in kmain()

This worked on the real device. #40

[kkebo]

I previously thought that I should use a singleton for Framebuffer because mboxCall() must be called only once. However, there are other methods that can achieve it. Moreover, there is the disadvantage that parameters cannot be passed from the outside.

So I have decided not to use a singleton.