AMD vs. Intel is a great analogy, really (there was Cyrix and others, as well). Try to understand it. And in the end, both have benefited from it; AMD has reproduced the Intel's interface, and later, Intel has reproduced the AMD's interface (AMD64) when it worked out better.
Not at all in comparison with GD32. AMD licenses out AMD64 extensions to Intel, likewise Intel licenses out x86 to AMD and others.
Wikipedia x86, x86-64:
Nevertheless, of those, only Intel, AMD, VIA Technologies and DM&P Electronics hold x86 architectural licenses, and from these, only the first two are actively producing modern 64-bit designs.
x86-64/AMD64 was solely developed by AMD. AMD holds patents on techniques used in AMD64;[90][91][92] those patents must be licensed from AMD in order to implement AMD64.
This is why private processor extensions can be such a crud to deal with.. Software compatibility was usually best on Intel because they had the fastest cores for a long time with the most extensions. The only thing AMD could do is to get a hold of, and implement the same instruction sets:
https://www.extremetech.com/computing/227059-amd-announces-new-293-million-joint-venture-to-build-servers-for-the-chinese-marketLisa Su also noted that the new joint venture would rely solely on AMD’s own intellectual property. This raises some significant questions about what, exactly, AMD can license. One of the problems with trying to talk about the x86 patent agreements between Intel and AMD is that what we refer to as “x86” is a collection of dozens of patents filed over decades by both companies. Intel still holds patents on major features like SSE4.x, AVX, and AVX2, while AMD has patents for AMD64.
So unless Gigadevice has paid STMicroelectronics a bag of money to use their patents, they might be infringing them.
On the other hand, how much is there to patent about the RTL of a part? And then I mean the programmer facing part; the bits that are in the registers... is that copyrighted? Patented? Do you claim binary or source code compatible? I think that is very debatable as it's mostly 'software'. A bunch of structs and memory address. How much is there infringing about it?
The actual HDL source code is covered by copyright. If Gigadevice would be forced in court to show sources and IF they would show 'stolen' or 'leaked' code from ST, I'm sure they will be in big trouble. But I think that it's far more likely that they have cloned the same functionality in their spare time. If you look closely at many "clone" devices you often see that high design effort features like power saving or mixed-signal (ADC, DAC) are terrible. It is often relatively simple to get something to work, but to perfect and polish it is 80% of the design effort. Likewise it is relatively simple to get a large databus in an MCU working at several tens of MHz, but if it then also must be power efficient such that you can compete on uA/MHz or <1 uA sleep mode, not so much. *This* could be a major part where vendors like ST, Atmel, Microchip, NXP, Silabs, Nordic, etc all have their own special sauce and patents in. And this is also exactly the reason why I'm sincerely looking forward for RISC-V devices specifically from those vendors, because the actual CPU core used can be an ill predictor for actual power efficiency (e.g. look at how much more efficient STM32L4 devices can be compared to STM32L1 or STM32L0), and a little while ago I checked out a RISC-V CPU that looked great.. except it still ran at 1mA/MHz or something.