Jump to content

Talk:x86-64

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Jeh (talk | contribs) at 18:56, 11 March 2019 (→‎Is it also aa64?: NO.). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Template:Vital article

WikiProject iconComputing C‑class High‑importance
WikiProject iconThis article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
CThis article has been rated as C-class on Wikipedia's content assessment scale.
HighThis article has been rated as High-importance on the project's importance scale.
Taskforce icon
This article is supported by Computer hardware task force (assessed as High-importance).



Hello fellow Wikipedians,

I have just modified 4 external links on X86-64. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

checkY An editor has reviewed this edit and fixed any errors that were found.

  • If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
  • If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 11:40, 3 September 2017 (UTC)[reply]

Possible Confusion: Image vs Image Caption

A small detail, I know -- I found it confusing that the caption on the X86-64 page says "Opteron, the first CPU to introduce the x86-64 extensions in 2003" while the inset image clearly shows a copyright date of 2001 printed on the CPU. It immediately begged the question "which is it: 2001 or 2003?" Documentation, both here and externally, agree that the official Opteron release date was 2003.

Perhaps the image is of a prerelease unit? The model number "OSA146DAA5BN" indicates an OEM/non-retail CPU. The OEM aspect implies it was likely produced for system builders like Dell, HP, Compaq, or Gateway. These companies would have needed some prerelease CPU's for development and initial release. That could explain the 2001 date. Except... Adding to potential confusion, this model wasn't actually released until 2005 (at least, according to the list of AMD Opteron microprocessors).

I don't know if it is possible to find an image of an Opteron CPU with a 2003 copyright date, much less of a model that was also released in 2003. I feel this would be the ideal solution. I know that copyright dates don't always align with release dates, but a 2 year difference feels extreme. A quicker-and-good-enough solution might be to drop the "in 2003" from the image caption. I could make the edit myself, but would appreciate the opinions/involvement of experienced editors.

-- GG Crew (talk) 06:36, 7 January 2018 (UTC)[reply]

I believe the copyright seen on that chip is for the AMD logo.War (talk)
+1. Guy Harris (talk) 20:04, 7 January 2018 (UTC)[reply]
Doubtful. Graphic designs that are "standalone" can be copyrighted (as the expression of a creative idea) but if they're used as part of a company or product's identity, they're trademarked or servicemarked. Either way there's still no problem here. Jeh (talk) 21:04, 7 January 2018 (UTC)[reply]
I'm not seeing a conflict. Copyright on a design can long predate the first production of a chip that implements the design. For that matter, copyright on a book manuscript can long predate its first printing. At least in the US, the copyright exists the moment it's written. Jeh (talk) 18:07, 7 January 2018 (UTC)[reply]

Correct naming - x64 and Intel 64

About the naming in the very first line; I think it should be distinguished that "x64" is NOT a correct way of referring to the 64-bit x86 (and to a certain extent neither is "Intel 64", although Intel themselves use it; it implies Intel's 64-bit Itanium which does exist, as much as some would like to forget it). I've seen many people confused why the 32-bit version is x86 and not x32 when the 64-bit is called x64; it's of course not x64 and this leads to initial confusion. I wouldn't like to see the same situation that we got when x86 was extended from a 16-bit address space pointers to a 32-bit one but it was still called "x86" and not e.g. "x86-32" to indicate the change. We indicate(d) other extentions (SSE, MMX), so why not something as big as the extention of address space? It's a small thing and you'd be right to say I'm getting hung up on naming, but I'd argue language and naming things is something very important since that's what allows us to communicate, learn and discuss; neglecting to name things correctly inevitebly leads to problems when we try to do the three things mentioned. I propose just a small change, such as "also known as x86_64, AMD64, incorrectly as x64, Intel 64" while leaving the note in place. — Preceding unsigned comment added by 85.163.18.131 (talk) 12:52, 22 July 2018 (UTC)[reply]

Who defines what's "correct"? AMD? Intel? AMD and Intel?
x64 may not be used by AMD or Intel, but it is used by Microsoft and Sun^WOracle, so, "correct" or not, it is used, and that probably should be noted.
Intel uses "Intel 64"; it doesn't imply Itanium - some people might incorrectly infer Itanium, but those people may not be aware that the Itanium architecture used to be called "IA-64", with the existing 32-bit version of x86 being called "IA-32". That meant that Intel couldn't call their flavor of x86-64 "IA-64" and they wanted to come up with some name for their flavor of x86-64; "AMD64" was unlikely to be chosen, for obvious reasons, so they imitated AMD and called it "Intel 64".
So, for better or worse, it's referred to as "x64" and "Intel 64" by organizations whose use can't simply be dismissed as "incorrect". Yes, those names may cause confusion, but that's what happens with names chosen by marketing departments; it's just something we have to live with, because Wikipedia is extremely unlikely to be able to effect any change there. Guy Harris (talk) 20:27, 22 July 2018 (UTC)[reply]
Agree with Guy Harris. x64 is very commonly used in the industry. We're not in a place to declare that it's "wrong". Jeh (talk) 04:58, 23 July 2018 (UTC)[reply]
My line of thinking was: the x86 name comes from the x86 naming of Intel's processors (80286 and 80286, 286 and 386 for short, hence x86), where does x64 come from? I don't remember an iconic line of processors using a similar naming scheme, the closest that comes to mind is the Athlon 64 line. Again, I'm being pedantic but as I already stated, there's nothing wrong with pointing wrong (or at least illogical) naming, regardless whether a couple of "industry leaders" use it. I also take back labeling Intel 64 as incorrect (although it still is illogical, Intel Architecture 32 is the 32-bit x86, IA-64 is Itanium, AMD64 is the widely implemented 64-bit x86 extention; Intel 64 = Itanium, AMD 64 = x86-64, seems simple enough for me). — Preceding unsigned comment added by 85.163.18.131 (talk) 08:15, 23 July 2018 (UTC)[reply]
I have no clue how marketing-department minds work, so I have no clue where "x64" comes from - and my curiosity about it is mild, at best. Why didn't IBM go from "System/370" to "System/380" when they added 31-bit-addressing support in 1980, but went with "System/390" in 1990 when no change that significant was made, for example? Or why did Apple go from "Mac OS X" to "OS X", several years after a non-Mac derivative, iOS, came out, rather than just going directly to "macOS"? Illogical, maybe, but, even if a lot of people might find a name illogical, I don't see any need for the Wikipedia to point that out. Guy Harris (talk) 11:15, 23 July 2018 (UTC)[reply]
To the IP: If Wikipedia were to state in its own voice that the "x64" name was "wrong" or even "illogical", regardless of reasoning, then Wikipedia would be expressing an opinion. We don't do that. See WP:NOTESSAY, which is part of our policy. We can report on opinions of recognized experts, but WP:N then requires that we give WP:DUE attention to all countering opinions, other than WP:FRINGE ones. And given the popularity of the "x64" name I'd say yours qualifies as WP:FRINGE. So, what can you do? Write your opinion on your own blog, or on a Facebook post, or maybe write it up and send it to a tech blog. But Wikipedia is not the place for your opinion or even your own reasoning. In fact, since article talk pages are not for general discussion about a topic but are supposed to be specifically for discussing improving the article, and an editor's opinion will not ever be allowed as part of the article, even the discussion here is borderline. Jeh (talk) 12:42, 23 July 2018 (UTC)[reply]

Is it also aa64?

aa64 is mentioned, for example, at https://github.com/pbatard/uefi-simple/commit/3250411a643b8967d9ed724219a33aa8af3855f7 and http://lkml.iu.edu/hypermail/linux/kernel/0008.1/0809.html. My guess is it is an abbreviation for AMD Architecture 64. And yet another abbreviation for x86-64. Is it justified to add this acronym to the x86-64 entry? — Preceding unsigned comment added by 5.102.216.121 (talk) 18:24, 11 March 2019 (UTC)[reply]

No. Github commits, esp from .edu , are not reliable sources. Wikipedia is not for things someone made up one day. Jeh (talk) 18:56, 11 March 2019 (UTC)[reply]