In preprocess for getting platform PCD information, if meet error, put error into...

[mirror_edk2.git] / ReleaseNotes.txt

diff --git a/ReleaseNotes.txt b/ReleaseNotes.txt
index d3b5a719a9632443343acef3226dbb48b6de6e40..b9da6c308069e353e7c97f51ac34e6826fc211b9 100644 (file)
--- a/ReleaseNotes.txt
+++ b/ReleaseNotes.txt
@@ -246,6 +246,16 @@ system will be a superior choice for those wishing to compile with gcc.
 Make sure that you select the e2fsprogs development package when you install\r
 cygwin. It is necessary for the GenFvImage tool.\r
 \r
+----------------------------------------\r
+A Word on gcc for Processor Architectures\r
+----------------------------------------\r
+\r
+Currently gcc support is limited to IA-32 builds, generating IA-32 PE32 images. \r
+\r
+The X64 bit (Intel 64, etc.) support under the gcc compiler does not support the EFIAPI calling convention (as defined in the UEFI 2.0 specification Chapter 2), so it is not possible to build a working EFI image for an X64 environment.  Since the x64 gcc does not support the EFIAPI calling convention the x64 tools do not support generating a PE32+ image.  The EFIAPI calling convention is very similar to the Microsoft x64 calling convention.\r
+\r
+On Itanium® Processors the gcc compiler does not support generating a PE32+ image.\r
+\r
 -----------------------\r
 Notes on Documentation\r
 -----------------------\r