I can sign up to maintain XCODE. I think Rebecca has been running test builds with XCODE. The XCODE5 names comes from the compiler flags needing to change for Xcode 5. Yes 2013 called and wants it com

I’d also point out that x86 VMs use X64 (x86-64) PEI today and it works so the 32-bit/64-bit mix has nothing to do with UEFI/PI/edk2. In the PC ecosystem a single chipset family can power thousands of

Is there an issue with the SecSwitchStack too? Thanks, Andrew Fish > > > >

Sukumar, The LongJump.iii is just the nasm file after it has been post processed you should be able to look at it. If I look at mine I see. 44: rdsspq rax ... 49: incsspq rax Those are some funky x86

Rebecca, I got it to compile by doing this diff --git a/CryptoPkg/Library/OpensslLib/OpensslLibCrypto.inf b/CryptoPkg/Library/OpensslLib/OpensslLibCrypto.inf index cdeed0d073eb..72dbeb2795e8 100644 --

Sorry I forgot to mention I was using an Xcode clang on macOS. Thanks, Andrew Fish

Gerd, I’m not sure if this was caused by my email client but your fix did not work for me. GNUmakefile:17: *** missing separator. Stop. I had to add a space after `ifeq` to get it to work. diff --git

From an UEFI point of view if you own the memory you can do what you want with it. The UEFI Spec does not deal with paging but the PI Spec does have abstractions for how the CPU operates via the CPU A

Rebecca, That would be awesome. I’m happy to help, and answer questions. I’ve been kind of swamped in my day job lately so this would really help. Thanks, Andrew Fish

Just throwing out an idea for the edk2 unit tests. At least for clang you can turn on the sanitizer via a simple command line flag to the compiler. So seems it would make sense to turn on it for unit

Mike, Yea I’m thinking this is a good reason to maybe not add more knobs. I was trying to get tricky and have code conditionally use a global so I could use the lib XIP when I shot myself in the foot.

I shot my self in the foot with the Fixed* macro in a library so I did not get the drivers override. So I feel that pain. You need to used the non Fixed form from a lib to get the value from the globa

Well it does seem like a reasonable thing to be able to do? What do other people think? I was able to refactor my code and I did not actually end up needing to override every PEIM and the PEI Core. Th

Mike, That is what I ended up doing, but it required overriding every PEIM and PEI Core. Seemed kind of excessive. I think people cheat and use IA32 vs X64 to mean PEI vs. DXE on X64 platforms. Thanks

I’m trying to have a different platform policy for PcdDebugPropertyMask in PEI and DXE. I can’t figure out how to do without overriding every PEIM that I build? My PEI and DXE has the same arch so I c

So I’m messing about in a DefaultExceptionHandler() (like [1]) that is called from CommonCExceptionHandler() [2]. What I notice is the faulting address is special cased. So the stack walking code has

Ray, ProcessSystemContext may not be needed… My thinking was if you pass ProcessSystemContext == TRUE there is some implied processing of the SystemContext by the PanicLib. If you pass FALSE then ther

Mike Kinney mentioned at the TianoCore Stewards Meeting that it might be a good idea to add a panic API to the edk2. I agree. Some background…. While ASSERT is a powerful tool I think we have a tenden

Mike, That sounds like the right fox to me. Disable the warning.

In general is it bad to assume what the disk node is going to look like. You have know idea what the transport is going to look like and how that transport enumerates disks. As I mentioned the BlockIO