amd64? When compiler on macOS, it's DEFINITELY x86_64. Isn't it the same in MinGW?
On Apr 29, 2018, at 12:00 PM, pd-dev-request@lists.iem.at wrote:
On 04/28/2018 02:04 AM, Thomas Mayer wrote:
Hi,
what should the string for MARCH be in the deken file name for Intel compatible processors, the deken documentation is unclear here:
- 64 bit: amd64 or x86_64?
AFAIK both mean the same thing, but are used in different contexts, most Linux distros use amd64, while on Windows x64 (Visual Studio) and x86_64 (MinGW) are used, no idea about Mac.
use "amd64" (although "x86_64" is allowed as well, the former is more concise and used by the 'deken' cmdline utility)
-------- Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
On 2018-04-29 21:46, Dan Wilcox wrote:
amd64?
yes, "amd64".
its an easy to remember, hard to confuse, well established term used for that architecture. "x86_64" is probably slightly more correct on the technical side, but a beast of a name (given that the full arch specifier consists of 2 more terms and they are separated by dashes - visually very similar to underscores). so the only drawback is, that uses a companies name ("amd"), even though the processor might be produced by another company ("intel").
however, we also call the corresponding 32bit architecture "i386" resp "i686" ("intel"; regardless of the producer) rather than the more correct "x86" (or was it "x86_32"?)
anyhow, the "find externals" plugin treats both "amd4" and "x86_64" as equivalent.
so, i was really answering the question "what *should* be used", and i think that "amd64" *should* be used, whereas "x86_64" *could* also be used if need be.
When compiler on macOS, it's DEFINITELY x86_64. Isn't it the same in MinGW?
could you clarify how you define "it"?
fgasdrm IOhannes
-
Dan Wilcox -
IOhannes m zmoelnig