Для работы проектов iXBT.com нужны файлы cookie и сервисы аналитики.
Продолжая посещать сайты проектов вы соглашаетесь с нашей
Политикой в отношении файлов cookie
SpaceMareen
Новичок
SpaceMareen
Рейтинг
+286.30
Автор не входит в состав редакции iXBT.com (подробнее »)
.
Moore expects AMD to see desktop PC-related revenue fall 26% year-over-year in 2022 and 2% in 2023, and lose some market share due to the success of Intel's Alder Lake processor in the gaming market. However, Moore said AMD should see «relative stability thereafter.»
* На самом деле больше, лицензия позволяет менять ISA как угодно на какие угодно, хоть на проприетарные. Ни на х86, ни на ARM такой ахинеей с разведением зоопарков заниматься не разрешено.
.
The four base ISAs in RISC-V are treated as distinct base ISAs. A common question is why
is there not a single ISA, and in particular, why is RV32I not a strict subset of RV64I? Some
earlier ISA designs (SPARC, MIPS) adopted a strict superset policy when increasing address
space size to support running existing 32-bit binaries on new 64-bit hardware.
The main advantage of explicitly separating base ISAs is that each base ISA can be optimized for its needs without requiring to support all the operations needed for other base ISAs.
For example, RV64I can omit instructions and CSRs that are only needed to cope with the narrower registers in RV32I. The RV32I variants can use encoding space otherwise reserved for
instructions only required by wider address-space variants.
https://riscv.org/technical/specifications/
.
+1, из-за него куча проблем, которых у других архитектур нет.
.
As a case study intended to evaluate the applicability of TriCheck to modern ISA design, we used TriCheck to evaluate the latest version (at the time of our study) of the RISC-V ISA’s [WLPA16]9 memory consistency model on its ability to support C11 programs. In doing so, TriCheck identified and characterized a series of deficiencies in the 2016 RISC-V memory model specification rendering it incompatible with C11. More concretely, TriCheck discovered that it was possible to build legal RISC-V implementations that satisfied the 2016 specification [WLPA16] yet could not run all valid compiled C11 programs correctly regardless of how the compiler was designed. In the process of evaluating the RISC-V memory model, TriCheck also identified two counterexamples to a previously proven-correct compiler mapping from C11 onto the Power and ARMv7 ISAs. This result along with concurrent work led to the discovery of flaws in the C11 memory model itself [MTL+16,LVK+17].