@Liming, @Leif: are there any objections to these patches? I know it is unfortunate that we need to modify instructions as part of the ELF to PE/COFF conversion, but it is very

we need to locate the FSP Info Header by calculating offset dynamically to handle the scenario of FSP component is being rebased to different location. Cc: Maurice Ma <maurice.ma@...> Cc:

1.--autodefault option VfrCompile will generate default opcodes for questions if some default are missing. 2 --checkdefault option VfrCompile will check whether every question has no default

The function CheckQuestionOpCode is to check whether the opcode is question opcode, but it misses two question opcodes: 'EFI_IFR_REF_OP' and 'EFI_IFR_RESET_BUTTON'. Now add them. Cc: Liming Gao

patch 1 is to fix a bug in current code. patch 2 is to add two compile option for VfrCompile. Cc: Liming Gao <liming.gao@...> Cc: Eric Dong <eric.dong@...> Contributed-under: TianoCore

(adding back our friends on cc) CoffAddFixup() must be used for absolute symbol references only. These instructions contain relative symbol references, which are recalculated in

(Apologies, missed out on this branch of the thread on first pass since I was dropped from cc.) Since I was not certain of how this was historically, or should in the future, be interpreted I left

Reviewed-by: Fu Siyuan <siyuan.fu@...>

Reviewed-by: Ye Ting <ting.ye@...>

The bug is caused by using already freed memory. If there is already an attempt and execute 'reconnect -r' command, all the AttemptConfig structure will be freed, but the mCallbackInfo->Current is

I don't object to using UINTN and UINT64 interchangeably in a file that is specific to an architecture where they resolve to the same thing. The thunking code is a bit clunky, and tries to deal with

[Steven]: In this example, the pie.o is just the object file which is not linked. And if you link this pie.o file, the linker will solve all these three R_X86_64_REX_GOTP symbol with same 'int n'

Hi Feng, For the record, http://opensource.org/licenses/bsd-license.php is the same as http://opensource.org/licenses/BSD-2-Clause. Which is mentioned explicitly under point 5 of the

While I don't disagree, the PI dependency expression instruction set (section 10.7, PI spec 1.4 vol2) does not look Turing complete to me. Meaning it's "binary" in much the same way a .uni file

This adds support for GCC 5.x in LTO mode for IA32, X64, ARM and AARCH64. Due to the fact that the GCC project switched to a new numbering scheme where the first digit is now incremented for

When building with LTO enabled, the LTO routines infer from the 'hidden' visibility of the _ModuleEntryPoint symbol that its code only needs to be retained if it is referenced internally, and

Recent versions of GNU ld automatically emit a .notes section into the ELF binary containing a build id. Since this is an allocatable section by default, it will be identified by GenFw as a

GCC in LTO mode interoperates poorly with non-standard libraries that provide implementations of compiler intrinsics such as memcpy/memset or the stack protector entry points. Such libraries need to

To accommodate upcoming GCCx toolchain versions that require 'gcc' to be used as the linker in order to support LTO, switch GCC44 and later (including CLANG35) to a new DLINK build rule that invokes

Before we can make non-backward compatible changes to the GCC build rules regarding the use of the 'gcc' binary as the linker, clone the existing GCC build rules into a 'GCCLD' build rule family, and