Build fix with gcc 4.1
PATCH 1/1 Build fix with gcc 4.1
The attached patch fixes these build errors I see with gcc 4.1:
cc1: warnings being treated as errorshvm.c: In function '__hvm_copy':
hvm.c:687: warning: 'p2mt' may be used uninitialized in this function
cc1: warnings being treated as errorshvm.c: In function 'hvm_set_cr3':/home/cegger/src/xen-mca-unstable.hg/xen/include/asm/p2m.h:122:
warning: 'p2mt' is used uninitialized in this function
cc1: warnings being treated as errorshvm.c: In function 'hvm_set_cr0':/home/cegger/src/xen-mca-unstable.hg/xen/include/asm/p2m.h:122:
warning: 'p2mt' is used uninitialized in this function
cc1: warnings being treated as errorssvm.c: In function 'svm_vmexit_handler':/home/cegger/src/xen-mca-unstable.hg/xen/include/asm/p2m.h:122:
warning: 'p2mt' is used uninitialized in this function
Signature · 12 lines
AMD Saxony, Dresden, Germany Operating System Research Center Legal Information: AMD Saxony Limited Liability Company & Co. KG Sitz (Geschäftsanschrift): Wilschdorfer Landstr. 101, 01109 Dresden, Deutschland Registergericht Dresden: HRA 4896 vertretungsberechtigter Komplementär: AMD Saxony LLC (Sitz Wilmington, Delaware, USA) Geschäftsführer der AMD Saxony LLC: Dr. Hans-R. Deppe, Thomas McCoy
xen/include/asm-x86/p2m.h +1 -1
@@ -119,7 +119,7 @@ static inline mfn_t gfn_to_mfn_current(uif ( ret ==0 ) { p2mt =p2m_flags_to_type (l1e_get_flags (l1e)); -ASSERT (l1e_get_pfn (l1e) !=INVALID_MFN || !p2m_is_ram (*t)); +ASSERT (l1e_get_pfn (l1e) !=INVALID_MFN || !p2m_is_ram (p2mt));if (p2m_is_valid (p2mt) ) mfn =_mfn (l1e_get_pfn (l1e));else
_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel