[haiku-development] Re: Fixing get_cpu_model_string(), Ticket 3541

  • From: André Braga <meianoite@xxxxxxxxx>
  • To: "haiku-development@xxxxxxxxxxxxx" <haiku-development@xxxxxxxxxxxxx>
  • Date: Sat, 20 Jun 2009 17:57:42 -0300

Em 20/06/2009, às 15:08, Christian Packmann <Christian.Packmann@xxxxxx> escreveu:

I don't think that this string generation should be part of a OS API, at least not in the kernel. OTOH, if the OS has the code to generate these strings anyway (sysinfo), then it may make sense to move the routines to a library and make them available for other programs which may want to use this information to display it another form (GUI instead of CLI).

And while you are at it, how about drafting an Acceleration Kit? It could abstract vector code running on the CPU or in the GPU, with hints for which would be more desirable if available. It might make sense to look at what Apple did with Accelerate.framework and OpenCL and devise an unified API that targets both worlds.

Be was doing something not quite along these lines, but just as interesting, with the (unreleased) OpenGL kit, where native code would be generated to make for missing GPU capabilities. Apple does this today with LLVM to make up for the lack of... everything interesting, on integrated Intel GMA graphics.

Again, it might make sense to leverage LLVM for on-the-fly code generation that covers both cases. Unfortunately we can't use LLVM to compile the whole OS given incomplete C++ support, but this is bound to change. The FreeBSD people are already testing building kernel +world with LLVM, and there are just a few issues left with #pragma's on contributed code, IIRC.

[/llvm_plug]


Cheers,
A.

Other related posts: