2010年1月27日 · 80386/i386 was the first 32-bit Intel processor. When it was introduced, lot of compilers started using i386 as a flag to turn code-generation for it, a name for various temporary files, and architecture denominations in file names. 80386 was succeeded by 486, 586 (aka Pentium) and the rest of the x86 architecture CPUs.

2013年3月18日 · i386 refers to the 32-bit edition and amd64 (or x86_64) refers to the 64-bit edition for Intel and AMD processors. Wikipedia's i386 entry: The Intel 80386, also known as the i386, or just 386, was a 32-bit microprocessor introduced by Intel in 1985... This is termed x86, IA-32, or the i386-architecture, depending on context. Wikipedia's x86_64 ...

2009年11月23日 · i386 is for 32 bit processors. All Core 2 Duos are capable of running 64 bit operating systems and 32 bit operating systems. You want x86_64 as it will run better and allow you to have more RAM in the future, although if you are worried about compatibility, you could use i386. Personally I haven't had any problems with x86_64 on Linux.

2014年1月30日 · i386 is the name of the 32-bit instruction set first implemented by Intel in the 386 processor. It became dominant thanks to dirt-cheap PC hardware. x86-64 is the name of the AMD extension added to i386 to make it capable of executing 64-bit code. This is the one you have.

2017年5月4日 · The following information may help to resolve the situation: The following packages have unmet dependencies: libstdc++6:i386 : Depends: libc6:i386 (>= 2.18) but it is not going to be installed Depends: libgcc1:i386 (>= 1:4.2) but it is not installable E: Unable to correct problems, you have held broken packages.

i386 System calls in i386 Linux are implemented using the 128th interrupt vector, e.g. by calling int 0x80 in your assembly code, having set the parameters accordingly beforehand, of course. It is possible to do the same via SYSENTER , but actually executing this instruction is achieved by the VDSO virtually mapped to each running process.

2020年9月14日 · The following information may help to resolve the situation: The following packages have unmet dependencies. wine-stable : Depends: wine-stable-i386 (= 5.0.2~focal) wine32:i386 : Depends: libwine:i386 (= 5.0-3ubuntu1) but it is not going to be installed E: Unable to correct problems, you have held broken packages.

/usr/bin/ld: i386:x86-64 architecture of input file `send.o' is incompatible with i386 output /usr/bin/ld: final link failed: Invalid operation collect2: ld returned 1 exit status I have installed libc6-i386 gcc-multilib ia32-lib. Where could be the problem?

grub rescue> ls (hd0,msdos1)/boot/grub i386-pc/ locale/ fonts/ grubenv grub.cfg Grub Manual: Troubleshooting: GRUB only offers a rescue shell covers the basic recovery method described above For available commands and variables see Grub Manual: The list of command-line and menu entry commands and Special environment variables .

2018年10月18日 · What is the most reliable way to find out CPU architecture when compiling C or C++ code? As far as I can tell, different compilers have their own set of non-standard preprocessor definitions (_M_X86 in MSVS, __i386__, __arm__ in GCC, etc). Is there a standard way to detect the architecture I'm building for?