Movatterモバイル変換


[0]ホーム

URL:


Jump to content
WikipediaThe Free Encyclopedia
Search

Talk:ARM architecture family

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
Skip to table of contents
This is thetalk page for discussing improvements to theARM architecture family article.
This isnot a forum for general discussion of the article's subject.
Find sources: Google (books ·news ·scholar ·free images ·WP refs·FENS ·JSTOR ·TWL
This level-5 vital article is ratedB-class on Wikipedia'scontent assessment scale.
It is of interest to the followingWikiProjects:
WikiProject iconComputingHigh‑importance
WikiProject iconThis article is within the scope ofWikiProject Computing, a collaborative effort to improve the coverage ofcomputers,computing, andinformation technology on Wikipedia. If you would like to participate, please visit the project page, where you can jointhe discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing
HighThis article has been rated asHigh-importance on theproject's importance scale.
Taskforce icon
This article is supported byComputer hardware task force (assessed asHigh-importance).
Text and/or other creative content fromthis version ofARM architecture was copied or moved intoList of ARM microprocessor cores withthis edit on 13 June, 2011. The former page'shistory now serves toprovide attribution for that content in the latter page, and it must not be deleted as long as the latter page exists.
Text and/or other creative content fromthis version ofARM architecture was copied or moved intoList of applications of ARM cores withthis edit on 22 June, 2011. The former page'shistory now serves toprovide attribution for that content in the latter page, and it must not be deleted as long as the latter page exists.
Archiving icon
Archives

Index1,2,3,4



This page has archives. Sections older than720 days may be automatically archived byLowercase sigmabot III when more than 4 sections are present.


Arm is sentence case?

[edit]
Resolved
 –All instances of ARM capitalized except for references to the company.120.159.128.133 (talk)14:06, 9 October 2020 (UTC)[reply]

I've noticed that userUser:JBMagination has changed all references to "ARM" in this article to sentence-case "Arm", citing company trademark policy. Doesn't this violateMOS:TM, as most sources still use Arm capitalized as "ARM"?ViperSnake151 Talk 21:45, 22 June 2020 (UTC)[reply]

If it is, I will gladly revert it.JBMagination (talk)21:49, 22 June 2020 (UTC)[reply]
Please at least revert the names of the chips -- the CPU was never called the 'Arm1' but the ARM1, etc.MatthewWilcox (talk)12:44, 9 July 2020 (UTC)[reply]
@ViperSnake151: Are you thinking ofMOS:TMCAPS, which says

For trademarks that are given in mixed or non-capitalization by their owners (such asadidas), follow the formatting and capitalization used byindependent reliable sources.

Note, though, that Arm isn't using mixed capitalization (if by that they meancamel case or stuff such as eBay and iPod) or non-capitalization, as they're capitalizing it proper-noun-style.
(This is a bit like Sun Microsystems, where the "Sun" originally came from theStanford University Network, for which the originalSUN workstation was designed, but - as I suspect I've said about a trillion times in USENET posts :-) - they were "Sun Microsystems", not "Stanford University Network Microsystems". The change from "ARM" to "Arm" didn't happen when the company was created, so it's notexactly the same, but it might be a bit similar.)Guy Harris (talk)22:49, 22 June 2020 (UTC)[reply]
I'm not sure about this change, but I think that ARM should be retainedat least in the history section to reflect the way it was written at that time. And what is used in official documents? (For instance, in France, the public institute INRIA has been deacronymized to Inria for the communication, but this has not been changed in legal texts yet.)Vincent Lefèvre (talk)09:33, 23 June 2020 (UTC)[reply]
  • Please revert. If there is a stylisation changegoing forward, then this can be reflected in the article, if/when the usage reaches wide-scale acceptance, ie. in the mainstream press. …The historical naming should probably remain as it has for the last ~35 years, since that is what is being reported/summarised in the majority of the article. TL;DR: ideallyARM1; or as an imperfect compromise, formatted asArm1 could also work. —Sladen (talk)13:40, 9 July 2020 (UTC)[reply]
  • Someone has gone through with a machete changing ARM to Arm - presumably what is referred to in this section. This includes all the historical references. The Acorn RISC Machine architecture was "ARM" not "Arm". There was never an "Arm610 microprocessor". etc. etc.Almost none of the usages of "Arm" in this article make any sense whatsoever. This article is not about the company which has renamed itself, and they cannot rewrite history. You'll note that even Arm themselves use "Arm" for the company and "ARM" for the architecture and the chips - e.g.https://developer.arm.com/documentation/den0024/a/armv8-a-architecture-and-processors/armv8-a - making these Wikipedia changes even more nonsensical --Davidcx (talk)20:37, 15 September 2020 (UTC)[reply]

Apart from anything else discussed just above, I would suggest altering the phrase "usually written as such today' to "often still written as such"NotesTracker (talk)12:15, 20 September 2020 (UTC)[reply]

Ironically ARM make AMD's x86 insecure?

[edit]

I've not yet read all thesecurity paper saying: "The AMD Secure Processor, the gatekeeper responsible for the security of AMD processors, contains critical vulnerabilities." Note theAMD Platform Security Processor (I assume the same thing), built into their x86 CPUs, is ARM with TrustZone.

It's not clear that the ARM core and/or TrustZone (never looked to closely at it) is to blame and most reporting doesn't mention ARM but ratherthe non-open source code it runs. It seems it is to blame, possibly not the core running it. Be aware of that before blaming ARM here on this page; this is just FYI, and for discussion here.

Other links maybe helpful (first one where I discovered this before looking up the others):

https://www.wired.com/story/amd-backdoor-cts-labs-backlash/

https://hothardware.com/news/amd-processors-and-chipsets-ryzenfall-chimera-fallout-security-flaws

https://www.amd.com/en/technologies/securitycomp.arch (talk)

No instruction set?

[edit]

ARM instruction set redirects here. Wouldn't it be better to list the instructions there? This page doesn't list the instructions, and I am looking for them, so I would greatly appreciate it.Joao003 (talk)17:18, 17 October 2023 (UTC)[reply]

It would be better not to list instructions on Wikipedia, at least for instruction sets with lots of instructions. I'm not sure whetherx86 instruction listings should exist, for example.
If you want ARM instructions, go tohttps://developer.arm.com/architectures and look through the search results for what you want.Guy Harris (talk)19:31, 17 October 2023 (UTC)[reply]

"No support for unaligned memory accesses in the original version of the architecture"

[edit]

Is this true? Per the ARM2 data sheet (emphasis added): "A word load (LDR) should generate a word aligned address.An address offset from a word boundary will cause the data to be rotated into the register so that the addressed byte occupies bits 0 to 7. External hardware could perform a double access to memory to allow non-aligned word loads"

To me that doesn't sounds like "no support" as this article currently claims; it clearly farms the stuff of doing two 32-bit accesses and combining parts of each to external hardware but appears to offer a helping hand should the system be set up to do that — the external bus merely needs to gate each of the four bytes to ensure it presents each from the correct access, it doesn't need to rotate them into place.

I'd call this negligible support, but not "no support".96.234.17.8 (talk)18:19, 28 March 2024 (UTC)[reply]

I agree. That's more a special behavior than no support. I'm wondering whether this was exploited in practice. —Vincent Lefèvre (talk)02:02, 29 March 2024 (UTC)[reply]

"ARM" and "Arm"

[edit]

I found that "ARM" has changed its name to "Arm", and now the documentation almost uses "Arm"

Arm Holdings#Name

For example document:https://developer.arm.com/documentation/ddi0487/ka#:~:text=Arm%20Architecture%20Reference%20Manual%20for%20A-profile%20architecture.%20For%20a%20listShiinaKaze (talk)12:25, 25 September 2024 (UTC)[reply]

AFAIK, this is not new. See the discussion#Arm is sentence case? above. —Vincent Lefèvre (talk)14:24, 25 September 2024 (UTC)[reply]

ARMv9.6-R and ARMv9.6-M

[edit]

Research the following and if you find any details about the following, please include them with their sources:


1) ARMv9.6-M

2) ARMv9.6-R78.190.164.190 (talk)15:44, 4 December 2024 (UTC)[reply]

I researched it and found that Arm have, apparently, never announcedany ARMv9-M or ARMv9-R architectures, much less a 9.6 version; there is, of course, no obligation whatsoever for Arm to offer, for every ARMv9.x-A version, a corresponding ARMv9.x-R or ARMv9.x-M version, so the lack of ARMv9.6-M or ARMv9.6-R is not particularly surprising. Thus, there are no details to include, other than, at most, their non-existence.Guy Harris (talk)08:08, 5 February 2025 (UTC)[reply]
Retrieved from "https://en.wikipedia.org/w/index.php?title=Talk:ARM_architecture_family&oldid=1274059022"
Categories:
Hidden categories:

[8]ページ先頭

©2009-2025 Movatter.jp