I noticed that in Library/SynchronizationLib.h the Interlocked functions (e.g. InterlockedIncrement) don't specify that the Value is volatile, but the InternalSync* functions they call in Synchronization.c _are_ specified as taking a volatile integer.
Is that due to the limitation imposed by the UEFI spec not having a VOLATILE modifier, or should they use the 'volatile' C keyword like the definition of SPIN_LOCK? -- Bruce ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ edk2-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/edk2-devel
