[ovmf baseline-only test] 66912: all pass

[Platform Team regression test user <citrix-osstest@xenproject.org>]

This run is configured for baseline tests only.

flight 66912 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/66912/

Perfect :-)
All tests in this flight passed as required
version targeted for testing:
 ovmf                 478f50990a9a3b76524fd14f2085b9f1127fa41a
baseline version:
 ovmf                 87ee6390cbeb2d15490943bca2978f166f213c13

Last test of basis    66909  2016-08-03 19:20:04 Z    0 days
Testing same since    66912  2016-08-04 01:19:57 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Ard Biesheuvel <ard.biesheuvel@linaro.org>

jobs:
 build-amd64-xsm                                              pass    
 build-i386-xsm                                               pass    
 build-amd64                                                  pass    
 build-i386                                                   pass    
 build-amd64-libvirt                                          pass    
 build-i386-libvirt                                           pass    
 build-amd64-pvops                                            pass    
 build-i386-pvops                                             pass    
 test-amd64-amd64-xl-qemuu-ovmf-amd64                         pass    
 test-amd64-i386-xl-qemuu-ovmf-amd64                          pass    


------------------------------------------------------------
sg-report-flight on osstest.xs.citrite.net
logs: /home/osstest/logs
images: /home/osstest/images

Logs, config files, etc. are available at
    http://osstest.xs.citrite.net/~osstest/testlogs/logs

Test harness code can be found at
    http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary


Push not applicable.

------------------------------------------------------------
commit 478f50990a9a3b76524fd14f2085b9f1127fa41a
Author: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Date:   Tue Aug 2 16:31:26 2016 +0200

    BaseTools GCC: add the compiler flags to the linker command line
    
    Now that we invoke GCC as the linker for the GCC toolchain family,
    we can pass the CC flags to the linker as well. This is only
    required for LTO (which may involve code generation during the link
    stage), but does not interfere with non-LTO builds.
    
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
    Reviewed-by: Liming Gao <liming.gao@intel.com>

commit f8d0b9662993796e89c200e9eaf38d1f54e5dd37
Author: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Date:   Tue Aug 2 16:15:31 2016 +0200

    BaseTools GCC5: disable warnings-as-errors for now
    
    GCC5 runs in LTO mode, which means it may generate code from an
    intermediate representation during the link stage, at which time
    additional diagnostics are run that may emit warnings.
    
    Some of these warnings seem to be spurious, e.g., the following
    warning which is emitted when building OVMF for IA32 or ArmVirtQemu
    for ARM (but not for X64 resp. AARCH64)
    
      .../MdeModulePkg/Library/UefiHiiLib/HiiLib.c:
                     In function 'HiiCreateGuidOpCode.constprop':
      .../MdeModulePkg/Library/UefiHiiLib/HiiLib.c:3228:10:
                     error: function may return address of local variable
                                                [-Werror=return-local-addr]
         return (UINT8 *)OpCodePointer;
                ^
      .../MdeModulePkg/Library/UefiHiiLib/HiiLib.c:3208:17: note: declared here
         EFI_IFR_GUID  OpCode;
                       ^
      lto1: all warnings being treated as errors
      lto-wrapper: fatal error: gcc returned 1 exit status
    
    So before adding the contents of CC_FLAGS to the linker command line,
    defuse the default '-Werror' by adding '-Wno-error' to DLINK2_FLAGS
    for GCC5.
    
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
    Reviewed-by: Liming Gao <liming.gao@intel.com>

commit 108c5b601860af0c3752d37e58e573e79a69c081
Author: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Date:   Tue Aug 2 15:38:58 2016 +0200

    BaseTools GCC: move -c compiler flag to build rules
    
    In order to be able to share the compiler flags with the linker (which
    is required for LTO since it involves the linker doing code generation
    based on the LTO bytecode), move the -c GCC argument to the build rules,
    and drop it from the GCC CC_FLAGS definitions in tools_def.
    
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
    Reviewed-by: Liming Gao <liming.gao@intel.com>

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel