Displaying 7 results from an estimated 7 matches for "mapkey".
Did you mean:
imapkey
2011 Jun 24
2
[LLVMdev] inefficiencies in ConstantUniqueMap ?
Hi,
Consider ConstantUniqueMap::getOrCreate() (in lib/VMCore/ConstantsContext.h):
/// getOrCreate - Return the specified constant from the map, creating it if
/// necessary.
ConstantClass *getOrCreate(const TypeClass *Ty, ValRefType V) {
MapKey Lookup(Ty, V);
ConstantClass* Result = 0;
...
For array (or struct or vector) constants, typically:
ValType = vector<Constant*>
ValRefType = ArrayRef<Constant*>
MapKey = pair<ArrayType, vector<Constant*>>
So am I right in thinking that the line:
MapKey Lookup...
2011 Jun 24
0
[LLVMdev] inefficiencies in ConstantUniqueMap ?
...Foad wrote:
> Hi,
>
> Consider ConstantUniqueMap::getOrCreate() (in lib/VMCore/ConstantsContext.h):
>
> /// getOrCreate - Return the specified constant from the map, creating it if
> /// necessary.
> ConstantClass *getOrCreate(const TypeClass *Ty, ValRefType V) {
> MapKey Lookup(Ty, V);
> ConstantClass* Result = 0;
> ...
>
> For array (or struct or vector) constants, typically:
>
> ValType = vector<Constant*>
> ValRefType = ArrayRef<Constant*>
> MapKey = pair<ArrayType, vector<Constant*>>
>
> So am I rig...
2020 Jun 11
2
[PATCH] efi/main: add retry to exit_boot()
Sometimes the UEFI memory map changes between GetMemoryMap() and
ExitBootServices(), making the MapKey value incorrect. Per the UEFI
spec, the memory map should then be fetched again and exiting retried.
Signed-off-by: Tom Huibregtse <thuibregtse at xes-inc.com>
---
efi/main.c | 81 ++++++++++++++++++++++++++++++++++++++++++++++--------
1 file changed, 70 insertions(+), 11 deletions(-)
diff...
2015 Nov 04
1
[PATCH] efi: Call ExitBootServices at least twice
...cessful, UEFI firmware memory allocation
>> should still be valid. I don't believe it's forbidden at all since
>> ExitBootServices() was NOT successful.
>
> I disagree with this. The documentation of ExitBootServices(), section
> 6.4, say (typo included):
> "If MapKey value is incorrect, ExitBootServices() returns
> EFI_INVALID_PARAMETER and GetMemoryMap() with ExitBootServices() must
> be called again. Firmware implementation may choose to do a partial
> shutdown of the boot services during the first call to
> ExitBootServices(). EFI OS loader shoul...
2020 Jun 18
0
[PATCH] efi/main: add retry to exit_boot()
...m Huibregtse via Syslinux" <syslinux at syslinux.org>
To: syslinux at syslinux.org
Sent: Thursday, June 11, 2020 8:04:06 AM
Subject: [syslinux] [PATCH] efi/main: add retry to exit_boot()
Sometimes the UEFI memory map changes between GetMemoryMap() and
ExitBootServices(), making the MapKey value incorrect. Per the UEFI
spec, the memory map should then be fetched again and exiting retried.
Signed-off-by: Tom Huibregtse <thuibregtse at xes-inc.com>
---
efi/main.c | 81 ++++++++++++++++++++++++++++++++++++++++++++++--------
1 file changed, 70 insertions(+), 11 deletions(-)...
2015 Nov 03
2
[PATCH] efi: Call ExitBootServices at least twice
On Mon, Nov 2, 2015 at 10:23 PM, Celelibi <celelibi at gmail.com> wrote:
> 2015-11-02 12:34 UTC+01:00, Gene Cumm <gene.cumm at gmail.com>:
>> On Tue, Aug 25, 2015 at 11:54 PM, celelibi--- via Syslinux
>> <syslinux at zytor.com> wrote:
>>> From: Sylvain Gault <sylvain.gault at gmail.com>
>>>
>>> Some firmware implementations may need
2015 Nov 03
0
[PATCH] efi: Call ExitBootServices at least twice
...f ExitBootServices is unsuccessful, UEFI firmware memory allocation
> should still be valid. I don't believe it's forbidden at all since
> ExitBootServices() was NOT successful.
I disagree with this. The documentation of ExitBootServices(), section
6.4, say (typo included):
"If MapKey value is incorrect, ExitBootServices() returns
EFI_INVALID_PARAMETER and GetMemoryMap() with ExitBootServices() must
be called again. Firmware implementation may choose to do a partial
shutdown of the boot services during the first call to
ExitBootServices(). EFI OS loader should not make calls to...