Opened 5 months ago

Closed 5 months ago

#18974 closed enhancement (fixed)

vulkan-loader-v1.3.272

Reported by: Douglas R. Reno Owned by: Douglas R. Reno
Priority: normal Milestone: 12.1
Component: BOOK Version: git
Severity: normal Keywords:
Cc:

Description

New point version

Change History (3)

comment:1 by Douglas R. Reno, 5 months ago

Owner: changed from blfs-book to Douglas R. Reno
Status: newassigned

comment:2 by Douglas R. Reno, 5 months ago

Fix typo in LoaderDriverInterface.md 
  Linux drivers use the ".so" extension, not ".dylib"
Cleanup loader_icd_init_entries 
  
  The logic of the function indicates that at a previous time, the
  functions being loaded used dlsym/GetProcAddress to query functions.
  Whenever that was changed to vkGetInstanceProcAddr, the error logging
  wasn't updated to remove loader_platform_get_proc_address_error.
  Trying to call dlerror() when no error has occured will return NULL,
  which was dutifully passed onto loader_log, causing crashes.

  The cleanup removes usage of that, as well as making the loading
  logic uses 2 macros, one for required & one for non-required
  function pointers.

  Cleanup also meant streamlining the parameter list of
  loader_icd_init_entries, since VkInstance and GetInstanceProcAddr
  are both able to be gotten from the icd_term. And also meant cleaning
  up the inst parameter being passed into loader_log, which was turning
  the drivers VkInstance into loader_instance* erroneously.

  A test was added to ensure that the error path when drivers do not
  support the required functions correctly returns an error from
  vkCreateInstance instead of crashing.
Improve warning message from terminator_CreateInstance 
  Old messages were clunky and lacked helpful info like which driver failed
  and the error code returned by the driver.
Fix settings file crash found through fuzzers 
  A few error conditions weren't properly handled whenever the settings file is invalid.
  Added the exact json file which caused the errors, then fixed issues with releasing
  memory properly.
proc_pidpath takes a uint32_t not a size_t 
ci: Test universal binaries 
Warn if apiVersion is below VK_API_VERSION_1_0 and above 0 
  Setting the apiVersion to an invalid value is an easy mistake to make.
  But because it causes drivers to fail, the validation layers can not catch
  it in time.

  This commit makes it a 'fatal error' which forces log_message to write out
  the message, regardless of whether or not VK_LOADER_DEBUG is set or if the
  application has setup a debug callback in the pNext chain.
Remove -fno-builtin-memcmp 
Remove API_NAME 
build(deps): bump github/codeql-action from 2.22.5 to 2.22.7 
Add Undefined Sanitizer support 
  Allows easy enabling of UBSAN.
  Fixes one issue found with UBSAN in the tests.
Remove -fno-strict-aliasing from builds 
  This was added in commit 7219950

  It was purported to fix a hang, but was never fully verified if it actually
  fixed the underlying issue (or if the issue came from buggy optimizing
  compilers or drivers).

  The chromium build does not enable -fno-strict-aliasing and hasn't had any
  issues known to be caused by strict aliasing optimizations.

  This commit also fixes debug report/debug utils code that was not properly
  casing to uintptr_t before assinging or dereferencing function parameters.
  The same logic occurs in wsi.h which as it assigned a pointer of VkIcdSurface
  to the VkSurface parameter.
Instance extensions unsupported by physical devices now return 
ERROR_EXTENSION_NOT_PRESENT
  This is makes the code gen for VK_EXT_acquire_drm_display be in line with the wsi code
  whenever calls to drivers are made which do not support the given extension.
build(deps): bump github/codeql-action from 2.22.7 to 2.22.8 
build: Update to header 1.3.271 
Test Xcode generator 
  Needed for iOS / simulator testing
Rename BUILD_STATIC_LOADER to APPLE_STATIC_LOADER 
  BUILD_STATIC_LOADER is ambiguous and implies it will work on all
  platforms.
  
  APPLE_STATIC_LOADER isn't ambiguous.

  Furthermore don't document BUILD_STATIC_LOADER. Otherwise users
  may use it when they shouldn't.

  Mark APPLE_STATIC_LOADER as advanced so it doesn't show up in
  cmake-gui by default.

  Furthermore, make the build fail if someone tries to use
  APPLE_STATIC_LOADER on a non Apple platform.
Add clang-format to CI 
docs: Remove comments about Travis/AppVeyor 
build: Update to header 1.3.272 

comment:3 by Douglas R. Reno, 5 months ago

Resolution: fixed
Status: assignedclosed
Note: See TracTickets for help on using tickets.