Are there any researches/works/agents into use LLM to auto covert some/all C code to Rust?

Ask LLM to generate rust code from chat, usb, i2c, GPU drivers - build and test it automatically? Possible?

Or start with other "smaller" projects such as sqlite, apache, nginx, etc - possible?

There's non-LLM research towards doing this which has a few success stories: https://github.com/immunant/c2rust

LLMs seem generally unsuited for the task, because they're fundamentally approximators that won't always get things right, and as a result will introduce subtle bugs. Perhaps if you paired them with some sort of formal methods... I'm not aware of anyone doing that. Tests aren't sufficient - lots of subtle bugs will not be caught by existing test suites.

Your idea of "smaller" projects is not... smaller enough. See the actual success stories for example: https://github.com/immunant/c2rust?tab=readme-ov-file#uses-o...

Darpa is interested in funding such an effort, but as far as I know that's the stage it's at, they haven't released any results.

Wonder if they manage to disable the UK's Trident Nuclear Submarine this time.

"Windows for Warship" https://en.wikipedia.org/wiki/Submarine_Command_System

"Want to Nuke someone, please send Bitcoin to unlock the systems."

https://www.theregister.co.uk/2017/06/27/hms_queen_elizabeth...

Is there a public link for that?

Part of the reason probably more biz related.

CEO/CFO of Intel looked at the balance sheet every Quarters and make decision if they should continue to invest in ARM SOC (A few years back before they sold that div to Marvell.)

x86 has 50% + margin, #1 market position.

ARM is #4,5, 6 in market position behind TI, Qualcomm, Freescale and lossing $$$ every quarters.

One need to investment huge amount of $$$ continuously fundamentally at IP for GSM, LTE, Mobile OS Team, SOC team and there were almost zero chance to catch up with #1 #2 players of the time -- Qualcomm, TI, 8-10 years ago.

It looks like this is putting 4 8 cores chips on the same package to scale up the cores counts, etc.

What are some of the technical limit to if AMD to 2, 4, 8x this approach?

Only power/heat? IO should not be hard since pins on MCM should be able to scale out easily, right?

There's going to be a hit to I/O when one of those modules needs to access RAM that's on a different module's controller. The new bus seems to be really fast though, so I'm not sure how many you get have before it's a real problem.

Supposedly the big innovation of the Zen platform is its interconnect tech managing to scale performance nearly linearly with more chips. Or so AMD claims.

I'd guess external IO (memory and PCIe) might be a problem. How are you going to route all those wires out from the socket?

Secondly, there's probably some economic argument as well. Too few customers willing to pay for a humongous MCM, and with the attendant wiring complexity requiring more layers for the motherboard, it might be cheaper to go to more sockets instead?

"Jack of all trades, master of none" is probably not a good way to increase share holder value.

Full quote: "...but often times better than a master of one"

That's a modern addition.

Sounds more like H-1B is just 21st century legal mean for the company to chain down those employees (like indentured servants of the past).

This also gives interesting overview of SDN, NFV, scale inside google data center.

https://www.youtube.com/watch?v=vMgZ_BdipYw

DOS is a acquired product, for $50k? :-)

They only finally disable cmd.exe in the latest update.

.bat files still run.

Somehow I overlooked that, but it's true, that's their first and most significant acquisition.

They didn't buy the company or talent, mind you, just the software.

According on this: http://kyokojap.myweb.hinet.net/gpu_gflops/

There were multiple factors of improvements in speed in the GPU inside last few generation of Intel CPU.

Unfortunately, folks who care about GPU performance likely use real graph card in their system.

There is zero growth in GPU performance from the 520 to the 620.

Just challenge the promoter to rewrite a c++ base program in their new favorite method, paradigm.

For example, the author of this paper can try to rewrite the google chrome browser - a huge C++ project in the "non-Harmful" way.

Rewriting is not very likely.

A new development could use a new paradigm. Same applies to goto vs structured programming, plain procedures vs classes and OOP-style method dispatch, etc.