On 4/3/2025 2:06, Jacek Caban wrote:
On 3.03.2025 14:22, Alvin Wong wrote:
I think both the current approach of lacking load config and the
proposed solution are fragile. Instead of relying on unrelated
linker warnings, if such a warning is necessary, it should be
implemented properly, with a
On 3.03.2025 14:22, Alvin Wong wrote:
I think both the current approach of lacking load config and the
proposed solution are fragile. Instead of relying on unrelated linker
warnings, if such a warning is necessary, it should be implemented
properly, with a clear message that users can understan
On 3/3/2025 4:32, Jacek Caban wrote:
On 2.03.2025 10:14, Alvin Wong wrote:
On 1/3/2025 20:25, Jacek Caban wrote:
This is mandatory on ARM64EC and also required on AArch64 for ARM64X
builds.
Instead of extending the existing logic, unify it by always
including it in mingwex.
In practice, this
在 2025-03-03 13:35, LIU Hao 写道:
Ideally there should always be a load config directory. If it is compiled into libmingwex then it's
not possible to turn it on or off at their disposal.
'their' = of a user who wishes to turn CF Guard on/off
GNU binutils does not support load config at the momen
在 2025-03-02 23:31, Alvin Wong via Mingw-w64-public 写道:
Honestly I've never thought about this before, so I just gave it a check on MSVC. Testing with the
version I have installed (19.35.32215), by comparing the output of `cl /PD /Zc:preprocessor
test.cpp` and `cl /PD /Zc:preprocessor /guard:cf
On 2.03.2025 10:14, Alvin Wong wrote:
On 1/3/2025 20:25, Jacek Caban wrote:
This is mandatory on ARM64EC and also required on AArch64 for ARM64X
builds.
Instead of extending the existing logic, unify it by always including
it in mingwex.
In practice, this means load config will always be pres
(Resending since SF rejected my original message)
On 2/3/2025 22:21, Martin Storsjö wrote:
I guess there's no prepreocessor define we can check in loadcfg.S, so
we'd need to pass one from the build system, when building with
--enable-cfguard, which can be used to switch between including or
On Sun, 2 Mar 2025, Alvin Wong wrote:
On 1/3/2025 20:25, Jacek Caban wrote:
This is mandatory on ARM64EC and also required on AArch64 for ARM64X
builds.
Instead of extending the existing logic, unify it by always including it in
mingwex.
In practice, this means load config will always be pre
On 1/3/2025 20:25, Jacek Caban wrote:
This is mandatory on ARM64EC and also required on AArch64 for ARM64X builds.
Instead of extending the existing logic, unify it by always including it in
mingwex.
In practice, this means load config will always be present in output images
when using
LLD. Si
On Sat, 1 Mar 2025, Jacek Caban wrote:
This is mandatory on ARM64EC and also required on AArch64 for ARM64X builds.
Instead of extending the existing logic, unify it by always including it in
mingwex.
In practice, this means load config will always be present in output images
when using
LLD.
This is mandatory on ARM64EC and also required on AArch64 for ARM64X builds.
Instead of extending the existing logic, unify it by always including it in
mingwex.
In practice, this means load config will always be present in output images
when using
LLD. Since ld.bfd does not support load config,
11 matches
Mail list logo
