cbmuser

62 ms·

691.
by cbmuser 7y ago
> sparc64 never made the switch (unfortunately) Care to elaborate? We're maintaining sparc64 in Debian Ports and we have smashed quite a number of bugs in the SPARC backend in LLVM. Are there any issues you are seeing?
692.
by cbmuser 7y ago
Neither is the PSX which you can easily buy used in Japan.
693.
by cbmuser 7y ago
After my last very successful Bountysource campaign to modernize the m68k backend ( https://www.bountysource.com/issues/80706251-m68k-convert-th... ) in GCC, I have decided to create another campaign to stimulate the dev
694.
Bountysource campaign to support the development of a Rust back end for GCC(bountysource.com)
1 points by cbmuser 7y ago|1 comments
695.
by cbmuser 7y ago
I cringed when he removed the CPU with a screwdriver from the board after spraying it with WD-40. First stating how rare these white 6502s are, then use brute-force methods to remove the chips off the board. He could have at least used a pr
696.
by cbmuser 7y ago
I disagree. The compiler is normally something that receives major updates in every new distribution release. That's why language specs exist for. If you are maintaining a large number of machines in an enterprise environment, you&#x27
697.
by cbmuser 7y ago
FWIW, you can even run the latest OpenJDK on m68k. In fact, here's is my Amiga 4000 running it on Debian unstable: root@elgar:~> dmesg |head [ 0.000000] Linux version 5.4.0-2-m68k (debian-kernel@lists.debian.org) (gcc versi
698.
by cbmuser 7y ago
I rather have 10 Fukushima nuclear accidents than one big dam break: > https://www.ozy.com/flashback/230000-died-in-a-dam-collapse-... Fukushima is mostly restored already: > https://www.japantimes.co.
699.
by cbmuser 7y ago
This is why I created the Bountysource campaign to fund the MODE_CC conversion of the m68k backend which luckily succeeded: > https://www.bountysource.com/issues/80706251-m68k-convert-th...
700.
by cbmuser 7y ago
What's a 1E8? I couldn't find an explanation on its meaning.
701.
by cbmuser 7y ago
Sounds very good. I'll keep an eye on the project. I would love to see such a frontend merged into GCC upstream and I would definitely shell out some money for a Bountysource campaign to support the effort.
702.
by cbmuser 7y ago
Ah, interesting. But can this implementation actually be built for architectures not supported by LLVM? I looked at the build instructions and the first build step involves building parts with the standard Rust compiler. I also just realize
703.
by cbmuser 7y ago
Compare the number of architectures by GCC: > https://en.wikipedia.org/wiki/GNU_Compiler_Collection#Archit... And the number of architectures by LLVM: > https://en.wikipedia.org/wiki/LLVM#Bac
704.
by cbmuser 7y ago
Which is the main reason why no usable alternative implementations exist yet and why Rust hasn't found its way to more low-level software projects like the Linux plumberland yet. Rust dearly needs a stable specification, it is the main
705.
by cbmuser 7y ago
GCC supports several targets like alpha, hppa, ia64, m68k, sh, v850 and vax (and more) that the LLVM-based Rust does not support because LLVM lacks support for these targets.
706.
by cbmuser 7y ago
And Amiga, Atari, 68k-Macintosh etc. FWIW, there is an out-of-tree m68k backend for LLVM [1]. I have already done some experimental work on Rust for m68k based on this backend [2]. > [1] https://github.com/M680x0/M68
707.
by cbmuser 7y ago
I have talked to GCC developers about integrating a Rust frontend and they said, the main blocker is the fact that the language specification isn't stable and a fast moving target. As long as the Rust language specification isn't
708.
by cbmuser 7y ago
Because you can just divide 30 by 365*24 to get the actual power which would be 3 Kilowatts or 0.003 Megawatts.
709.
by cbmuser 7y ago
This is a BountySource campaign I created that aims at funding the work on the AVR backend in GCC so it can be converted from the cc0 to the MODE_CC register representation similar to the m68k backend. Without this conversion work, the AVR
710.
BountySource campaign to modernize the AVR back end in GCC(bountysource.com)
2 points by cbmuser 7y ago|1 comments
711.
by cbmuser 7y ago
IBM still earns a lot of money with their mainframe and AIX business.
712.
by cbmuser 7y ago
It might be changed to "IN_PROGRESS" with Microsoft Edge being released for Linux next year :).
713.
by cbmuser 7y ago
20 years is a common number that is used for windparks and solar cells. A lot of sources cite that number. And that with capacity factors ranging between 10% to maximal 50%. Modern nuclear power plants (VVER-1200) reach 60 years of lifetime
714.
by cbmuser 7y ago
How are wind and solar cost-competitive when they can exist in Germany only with extreme high subsidies? Look at the new windfarm called "Wikinger" that Germany built near the island of Ruegen: https://de.wikipedia.org&
715.
by cbmuser 7y ago
Volkswagen isn't going to convert to electric anytime soon. Electric cars only make 1% of the annual car registrations in Germany and 0.18% of the total number of cars registered. In fact, Volkswagen is planning a new factory for cars
716.
by cbmuser 7y ago
Slightly off-topic: For anyone interested in the 68k architecture, there is a Bountysource crowd-funding campaign that aims help modernize the 68k backend in GCC so it can be kept in future versions (cc0 transition): > https:/&#x2F
717.
by cbmuser 7y ago
The m68k backend in gcc is one of the backends which hasn't gone through the CC0 transition yet [1, 2]. This campaign aims to collect donations for a bounty to pay a skilled developer to convert the m68k backend from CC0 to MODE_CC rep
718.
Bountysource campaign to save the m68k back end in GCC(bountysource.com)
4 points by cbmuser 7y ago|1 comments