Many thanks Jeff & David,
Overnight I remembered that Visual Studio itself offers a specific
option to disable inline function expansion. For MSVC itself, this gets
done by setting a compiler option called "/Ob" ("/Ob0" indicates
disabled). If "/Ob0" isn't specified at compile time, inlining
> ...
> I checked this morning and sure enough the "/Ob" option doesn't get sent
> if I build with VS2019 and Clang - so I'm guessing "/Ob0" wouldn't be
> recognised by Clang's compiler?
>
> So does Clang have it's own command-line option to disable inline
> function expansion? Or is that somethi
On 21/09/2021 13:49, Jeffrey Walton wrote:
The U&L option is -fno-inline. But I think Clang has an option to
consume MSVC style options, so you may be able to use /Ob.
I think you can check which MSVC style options Clang accepts with
'clang-cl /?' or 'clang-cl -?'.
Thanks again Jeff and you'
I just found something else which might be significant... I noticed
that when linking this exe, I had a linker option enabled called
/FORCE:MULTIPLE
If I remove that option, the Clang linker then gives me a list of about
a dozen duplicated symbols. And with that option I get a similarly
siz
