Skip to content
This repository has been archived by the owner on Oct 3, 2021. It is now read-only.

Darksea's bitwise termination bechmarks used in aplas21 paper. #1302

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

cyruliu
Copy link

@cyruliu cyruliu commented Aug 12, 2021

Dear SV-COMP Community,

We would like to contribute our bwb(Bitwise with Branching) termination benchmarks used in our work Proving LTL Properties of Bitvector Programs and Decompiled Binaries, which was accepted to APLAS'21, to sv-benchmarks. The benchmarks were added into the folder c/termination-bwb. Please let us know if there are any issues.

Thank you very much for your consideration. We are looking forward to your acceptance.

Best Regards,
On behalf of our team, Y. Cyrus Liu

  • programs added to new and appropriately named directory

  • license present and acceptable (in machine-readable comment at beginning of program as specified by the REUSE project)

  • contributed-by present (either in README file or as comment at beginning of program)

  • programs added to a .set file of an existing category, or new sub-category established (if justified)

  • intended property matches the corresponding .prp file

  • programs and expected answer added to a .yml file according to task definitions

  • data model present in task-definition file
  • original (ideally not preprocessed) sources present
  • preprocessed files present
  • preprocessed files generated with correct architecture
  • Makefile added with correct content and without overly broad suppression of warnings

@cyruliu cyruliu changed the title bitwise termination bechmarks used in aplas21 paper. Darksea's bitwise termination bechmarks used in aplas21 paper. Aug 12, 2021
@cyruliu cyruliu marked this pull request as draft August 12, 2021 21:33
@PhilippWendler PhilippWendler added C Task in language C new benchmarks labels Aug 13, 2021
@PhilippWendler
Copy link
Member

Thanks!

Two first comments that might be helpful already while this is in draft status:

  • As long as your .c files do not use #include, there is no need to preprocess them and add .i files. You can remove the latter.
  • We have started using the format proposed by REUSE for adding license and copyright notices. Please use this for all files (and then you can remove your LICENSE.txt). The reuse addheader tool can automate adding the license headers.

@cyruliu cyruliu marked this pull request as ready for review August 17, 2021 15:33
@cyruliu
Copy link
Author

cyruliu commented Aug 17, 2021

Hi @PhilippWendler ,

Thank you so much for the comments! I updated the license to REUSE format, and remove the unnecessary preprocess files, can you help to review the benchmarks? Please let me know if there are other issues, thank you!

Best,
Cyrus

@PhilippWendler
Copy link
Member

Thanks!

I noticed that the SPDX information is different from authors and license in the readme.md, which of these is correct?

And is this the full collection from https://graphics.stanford.edu/~seander/bithacks.html or just a few select examples? Because the license info on that page is a little bit unclear when someone copies the whole collection?

@cyruliu
Copy link
Author

cyruliu commented Aug 19, 2021

Hi @PhilippWendler,

The SPDX information should be used, and just a few selected code snippet examples are from bithacks public domain, for clarity, I update the content of readme.md, please check, thank you!

Best,
Cyrus

@PhilippWendler
Copy link
Member

Looks good, I guess.

Now which category should these be added to? Termination-BitVectors.set?

@cyruliu
Copy link
Author

cyruliu commented Aug 19, 2021

Hi @PhilippWendler ,

That sounds good, I didn't see Termination-BitVectors.set in the repo, it would be great if the benchmarks I'm submitting can be added to it, thank you!

@PhilippWendler
Copy link
Member

Yes, that would be a new subcategory. @dbeyer What do you think?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
C Task in language C new benchmarks
Development

Successfully merging this pull request may close these issues.

2 participants