diff options
| author | Martin Liska <mliska@suse.cz> | 2022-10-05 11:15:36 +0200 |
|---|---|---|
| committer | Martin Liska <mliska@suse.cz> | 2022-10-07 15:46:30 +0200 |
| commit | 1a308905c1baf64d0ea4d09d7d92b55e79a2a339 (patch) | |
| tree | e549294a5e42a24d75db24c9b32e25d17a03dadd /libcpp/include/cpplib.h | |
| parent | edbb2551d156d69a2e337dcd8daa69f2680d57ea (diff) | |
| download | gcc-1a308905c1baf64d0ea4d09d7d92b55e79a2a339.zip gcc-1a308905c1baf64d0ea4d09d7d92b55e79a2a339.tar.gz gcc-1a308905c1baf64d0ea4d09d7d92b55e79a2a339.tar.bz2 | |
IPA: support -flto + -flive-patching=inline-clone
There's no fundamental reason why -flive-patching=inline-clone can't
coexist with -flto. Yes, one can theoretically have many more clone
function that includes a live patch. It is pretty much the same
as in-module inlining.
gcc/ChangeLog:
* opts.cc (finish_options): Print sorry message only
for -flive-patching=inline-only-static.
gcc/testsuite/ChangeLog:
* gcc.dg/live-patching-2.c: Update scanned pattern.
* gcc.dg/live-patching-5.c: New test.
Diffstat (limited to 'libcpp/include/cpplib.h')
0 files changed, 0 insertions, 0 deletions