Jump to content

Talk:Intel ADX

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

Contested deletion

[edit]

This article should not be speedy deleted as having no substantive content, because... (your reason here) --Emperor-Overlord100 (talk) 19:18, 7 September 2013 (UTC) Not much in known about this instruction set extension but its existence was revealed in HWinfo. So J think it should stay so it be easy to add information to it when details will be revealed.[reply]

Not notable. No. Fiddle Faddle 19:42, 7 September 2013 (UTC)[reply]

It is notable information. — Preceding unsigned comment added by Emperor-Overlord100 (talkcontribs) 20:08, 7 September 2013 (UTC) And article already has some content.--Emperor-Overlord100 (talk) 20:55, 7 September 2013 (UTC)[reply]

Incorrect information re: arbitrary precision arithmatic

[edit]

According to the second article in the reference section, the ADX instruction set only allows large integer arithmetic, not arbitrary precision arithmetic. The former is a very small subset of the latter. Specifically, it doesn't allow arbitrarily large integer arithmetic, nor large floating point arithmetic. The wording should be corrected.Talcite (talk) 12:25, 12 January 2015 (UTC)[reply]

Please feel free to do it yourself, preferably together with providing references. — Dsimic (talk | contribs) 21:49, 14 January 2015 (UTC)[reply]

Expand

[edit]

Two of us have stubbed it independently, with one editor removing the stub twice and rating B. Well, if this is so short a topic that B is anywhere near the mark (which two of us believe it is more like a stub), then we may as well merge into a list of instructions (which I'm sure we shouldn't). A link to the former instruction would be good, and I'm sure there's other things... Regards Widefox; talk 21:55, 1 April 2016 (UTC)[reply]

reading the carry from the overflow flag???

[edit]

"Adds two unsigned integers plus carry, reading the carry from the overflow flag" Daroooo (talk) 10:25, 3 June 2019 (UTC)[reply]