this post was submitted on 11 Jun 2026
39 points (100.0% liked)

No Stupid Questions

48460 readers
811 users here now

No such thing. Ask away!

!nostupidquestions is a community dedicated to being helpful and answering each others' questions on various topics.

The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:

Rules (interactive)


Rule 1- All posts must be legitimate questions. All post titles must include a question.

All posts must be legitimate questions, and all post titles must include a question. Questions that are joke or trolling questions, memes, song lyrics as title, etc. are not allowed here. See Rule 6 for all exceptions.



Rule 2- Your question subject cannot be illegal or NSFW material.

Your question subject cannot be illegal or NSFW material. You will be warned first, banned second.



Rule 3- Do not seek mental, medical and professional help here.

Do not seek mental, medical and professional help here. Breaking this rule will not get you or your post removed, but it will put you at risk, and possibly in danger.



Rule 4- No self promotion or upvote-farming of any kind.

That's it.



Rule 5- No baiting or sealioning or promoting an agenda.

Questions which, instead of being of an innocuous nature, are specifically intended (based on reports and in the opinion of our crack moderation team) to bait users into ideological wars on charged political topics will be removed and the authors warned - or banned - depending on severity.



Rule 6- Regarding META posts and joke questions.

Provided it is about the community itself, you may post non-question posts using the [META] tag on your post title.

On fridays, you are allowed to post meme and troll questions, on the condition that it's in text format only, and conforms with our other rules. These posts MUST include the [NSQ Friday] tag in their title.

If you post a serious question on friday and are looking only for legitimate answers, then please include the [Serious] tag on your post. Irrelevant replies will then be removed by moderators.



Rule 7- You can't intentionally annoy, mock, or harass other members.

If you intentionally annoy, mock, harass, or discriminate against any individual member, you will be removed.

Likewise, if you are a member, sympathiser or a resemblant of a movement that is known to largely hate, mock, discriminate against, and/or want to take lives of a group of people, and you were provably vocal about your hate, then you will be banned on sight.



Rule 8- All comments should try to stay relevant to their parent content.



Rule 9- Reposts from other platforms are not allowed.

Let everyone have their own content.



Rule 10- Majority of bots aren't allowed to participate here. This includes using AI responses and summaries.



Credits

Our breathtaking icon was bestowed upon us by @Cevilia!

The greatest banner of all time: by @TheOneWithTheHair!

founded 3 years ago
MODERATORS
 

I'm very excited for RISC-V adoption in the desktop to become mainstream, as it could help to break the duopoly of x86 CPUs by Intel and AMD and encourage more competition, resulting in better value CPUs for us consumers! Being an open standard, any company can improve upon RISC-V, add additional features, make it more efficient, etc. But aside from this point, I haven't really heard much information about other advantages of RISC-V.

Could RISC-V theoretically be more efficient than ARM, more performant, etc.? Of course, currently, it isn't, since most software isn't optimised for RISC-V CPUs and companies have only just started developing them, but if it's adopted at a scale like x86 in desktop computers or ARM in mobile devices and servers, would it perform better than the x86 or ARM equivalent? Being a newer architecture (2014) than both x86 (1978 for 16-bit) and ARM (1985), does it have additional QoL improvements over the older architectures?

you are viewing a single comment's thread
view the rest of the comments
[–] adespoton@lemmy.ca 2 points 2 days ago (1 children)

While true, RISC-V probably isn’t the architecture for that. Better to use an old architecture whose patents have expired, and implement it on a new, smaller process.

RISC-V is good as an alternative to ARMv8 where the use case doesn’t quite fit what ARM is doing — or to implement in a country where there may be restrictions on how ARM is sold/deployed.

What I’m waiting for is for someone to implement something in RISC-V similar to Apple’s ARM implementation, with all the cores and memory on a single die. No need to do FPGA when you can just fab an unencumbered design in small batches for relatively cheap.

[–] litchralee@sh.itjust.works 0 points 2 days ago (1 children)

Better to use an old architecture whose patents have expired, and implement it on a new, smaller process.

I'm not aware of any examples of an old architecture that was largely reused while ported to a new process, without requiring extensive redesigning of the analog components. Old processor architectures are a product of their day, making assumptions and decisions about the silicon paths that would be wholly invalidated if brought as-is to more-modern processes. It is nowhere near as simple as a copy/paste job of SystemVerilog or RTL.

To invest even one hour of design time to update, say, the 1970s Intel 4004 design (10 micrometer process) into the 2000s (130 nm) would be more expensive than just using RISC-V for free, which has already been fabricated using 22 nm, among other processes.

[–] adespoton@lemmy.ca 1 points 2 days ago

The MC68000, for example, is over 40 years old and out of patent. It’s been repackaged on a smaller process as the 68SEC000, and there are Verilog implementations available too.

And that’s just the example that’s top of mind. There’s a whole line of low frequency Atmel processors too, but those are still very much in patent and so mostly tangential to this conversation.

RISC-V doesn’t really make sense for simpler implementations though; you’d still have to do a bunch of work to simplify it, AND end up with an architecture very few are currently familiar with.

Once Chinese implementations of RISC-V become endemic and there are enough people familiar with the architecture, it might make sense to start creating custom subsets on simplified processes. But we’re still years away from that.