The previously used syntax, -Wl,-pdb,<file>, was the originally
supported one in lld (since 2018). Later (in 2019) the second
syntax was added, allowing both -Wl,-pdb=<file> and -Wl,-pdb,<file>.
(This other parameter syntax allows easier distinguishing an empty
argument, for letting the linker implicitly pick the file name.)
Move over to using the more modern syntax - reducing the usage of
the old form of the option. This potentially allows deprecating
the original syntax and maybe allows using --pdb as a boolean
flag for implying an automatically named PDB file (which currently
requires using the awkward syntax "--pdb=").
Also prefer the long two dashes form, i.e. --pdb instead of -pdb;
the single dash form is only allowed by getopt when there
are no conflicts with single-letter options, while the form with
two dashes is unambiguous.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/1200
A mix of a miscellaneous fixes:
* Fixes to failed asserts I have stumbled upon when implementing other features.
* Checks required for properly supporting object components.
* A couple of code improvements.
--
v3: vkd3d-shader/hlsl: Use reg_size as component count when allocating a single register.
vkd3d-shader/hlsl: For arrays, return components' base type in sm1_base_type().
vkd3d-shader/hlsl: Validate that objects are not components of structs in shader models < 5.
tests: Add SM5 requirement to tests with object components.
vkd3d-shader/hlsl: Don't allocate object types as constant registers.
vkd3d-shader/hlsl: Make hlsl_type_get_component_type() type argument const.
https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/42
This change is adding DWARF (CFI) unwind information to the
hand-written assembly of the `__wine_syscall_dispatcher` function.
This enables unwinding through the dispatcher from the Linux stack
into (and through) the Windows stack.
The general idea is that the `syscall_frame` struct contains the
content of the callee-save registers before the function call
(in particular the stack pointer and the return address). At any
point of the execution, we have a pointer into the `syscall_frame`
in $ebx, $ecx, $ebp, or $esp.
For the CFI codes the general idea is that we are defining the
computations of the callee-save registers based on the
`syscall_frame` using DWARF’s `breg` instruction, rather than
relative to CFA.
cc/ @florian-kuebler
--
v2: ntdll: Add CFI unwind info to __wine_syscall_dispatcher (i386).
https://gitlab.winehq.org/wine/wine/-/merge_requests/1182
This series is mainly a change in internal structures for
describing functions:
- symt_function doesn't support multi range of addresses
- while symt_inlinesite does
That's the major difference between the two.
So the aim of this serie is to decribe function and inline sites with
a single structure.
--
v2: dbghelp: Get rid of symt_inlinesite by merging it inside symt_function.
dbghelp: Use addr_range for storing symt_function address and size.
dbghelp: Store address range as FAM in symt_inlinesite.
dbghelp: No longer pass inline site's address upon creation.
https://gitlab.winehq.org/wine/wine/-/merge_requests/1161