via llvm-dev
2021-Sep-22 14:25 UTC
[llvm-dev] Disabling inline compilation (Clang with VS2019)
> -----Original Message----- > From: llvm-dev <llvm-dev-bounces at lists.llvm.org> On Behalf Of John Emmas > via llvm-dev > Sent: Wednesday, September 22, 2021 10:13 AM > To: llvm-dev at lists.llvm.org > Subject: Re: [llvm-dev] Disabling inline compilation (Clang with VS2019) > > On 22/09/2021 15:00, paul.robinson at sony.com wrote: > > > It looks like the driver does translate "/Ob0" to the internal option > > "-fno-inline" which ought to prevent inlining of anything that is not > > marked as always-inline; > > > > Thanks Paul - does Clang produce some log file that'd tell me what > command got received from Visual Studio? VS tells me that it's sending > "/Ob0" but if it's working for you, it'd be nice to check here if "/Ob0" > actually got received. I've known things to stop working occasionally > in new VS revisions.I don't see a way to make Clang echo the original command line. You can add -v to the command line, which will report the internal command line passed from the driver to the compiler proper, and with /Ob0 you should see -fno-inline on that command line. --paulr
John Emmas via llvm-dev
2021-Sep-22 15:09 UTC
[llvm-dev] Disabling inline compilation (Clang with VS2019)
On 22/09/2021 15:25, paul.robinson at sony.com wrote:> You can add -v to the command line, which will report the internal command > line passed from the driver to the compiler proper, and with /Ob0 you > should see -fno-inline on that command line. >Yes that works. So it's strange that the inlining seems to be different for us (unless it's some other project setting??) John