You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, in the log below, cvise shows line reductions at first, going to a minimum of 16535, and then it increases back to ~20k lines of code. Is this behavior expected? I thought each local improvement served as a seed for the next iterations of the search pass.
This is with cvise 2.7.0 on Debian 11 (I checked the changelog and did not see highlights of later version on a similar topic).
00:00:25 INFO ===< ClangBinarySearchPass::replace-function-def-with-decl >===
00:00:31 INFO using C++ standard: c++2b with 841 transformation opportunities
00:00:50 INFO (29.9%, 3053083 bytes, 55930 lines)
00:01:09 INFO (64.0%, 1566001 bytes, 27923 lines)
00:01:25 INFO (69.7%, 1318397 bytes, 22762 lines)
00:01:41 INFO (71.6%, 1237631 bytes, 19426 lines)
00:01:58 INFO (73.2%, 1164978 bytes, 16535 lines)
00:02:15 INFO (72.4%, 1200532 bytes, 17088 lines)
00:02:31 INFO (72.0%, 1218095 bytes, 17085 lines)
00:02:51 INFO (71.8%, 1226490 bytes, 16754 lines)
00:03:11 INFO (72.3%, 1204802 bytes, 15649 lines)
00:03:33 INFO (72.4%, 1200571 bytes, 15235 lines)
00:03:55 INFO (71.5%, 1240837 bytes, 15775 lines)
00:04:15 INFO (70.5%, 1285107 bytes, 16334 lines)
00:04:31 INFO (69.5%, 1328775 bytes, 16874 lines)
00:04:46 INFO (68.4%, 1376447 bytes, 17433 lines)
00:05:03 INFO (67.3%, 1423517 bytes, 17973 lines)
00:05:25 INFO (66.1%, 1474591 bytes, 18532 lines)
00:05:48 INFO (65.0%, 1525063 bytes, 19072 lines)
00:06:07 INFO (63.7%, 1579539 bytes, 19631 lines)
00:06:34 INFO (62.5%, 1633413 bytes, 20171 lines)
00:07:01 INFO (61.1%, 1691291 bytes, 20730 lines)
The text was updated successfully, but these errors were encountered:
Yes, I have similar issues with the latest version. This was due to a dumb mistakes on my end, where I overwrote the generated file by a file getting bigger and bigger. I'm wondering, would it be interesting for cvise to:
detect that the file on which testcase reduction is performed has been overwritten?
warn during file increases (I don't think they should happen during reductions?)
Hi, in the log below, cvise shows line reductions at first, going to a minimum of 16535, and then it increases back to ~20k lines of code. Is this behavior expected? I thought each local improvement served as a seed for the next iterations of the search pass.
This is with cvise 2.7.0 on Debian 11 (I checked the changelog and did not see highlights of later version on a similar topic).
The text was updated successfully, but these errors were encountered: