profile
viewpoint

CSC322-Grinnell/boardbank 2

Connect community members with nonprofit board and volunteer opportunities.

zsusag/Grinnell-Linux-Printer-Installation 1

This repository contains the materials needed to get printers on the Grinnell College network working on a GNU/Linux system.

GrinnellAppDev/Lyles-Android 0

An Android application for Lyle's Pub

zsusag/AppDevDirectory 0

Trainee Project for Grinnell College's AppDev

zsusag/arduino-makefile 0

Generic Makefile to build Arduino .ino sketches from the command line

zsusag/Camera 0

An encrypted backup solution for GNU/Linux systems

zsusag/GrinHC 0

This is a compiler created for CSC-312 at Grinnell College during the Spring 2018 semester.

PR closed GrinnellAppDev/Lyles-Android

Schedule

This branch currently contains the bare bones of the schedule page using a RecyclerView.

+174 -34

0 comment

18 changed files

marcelchampagne

pr closed time in 7 days

push eventlahiri-phdworks/klee

lahiri.phdworks

commit sha e0a6071fad70ab5904bc408201f52c0cc27a6e7d

Tests Updated

view details

push time in 15 days

push eventlahiri-phdworks/klee

lahiri.phdworks

commit sha 82e3c2cdeda2351a9c3a1327e219fcb005e03040

Klean up KLEE

view details

push time in 15 days

push eventlahiri-phdworks/klee

lahiri.phdworks

commit sha 48a283a966f041c416d93254a17a8ae463bf45e6

Stable Logs generated via Dumping

view details

push time in 17 days

push eventlahiri-phdworks/klee

lahiri.phdworks

commit sha 470f1b04c9f8f7dee0228a671e1a0903fedc2ee5

Dumps Refined

view details

push time in 22 days

push eventlahiri-phdworks/klee

lahiri.phdworks

commit sha 927bcac16202f4df7fe0aa73c0565418fb4c3219

Simplied Dumps

view details

push time in 22 days

push eventlahiri-phdworks/klee

push time in 22 days

push eventlahiri-phdworks/klee

push time in 22 days

push eventlahiri-phdworks/klee

lahiri.phdworks

commit sha f0a1c6929f933b97f0334b8de0cfa05991afef82

Dumps Refined

view details

push time in 25 days

push eventlahiri-phdworks/klee

push time in 25 days

push eventlahiri-phdworks/klee

push time in a month

push eventlahiri-phdworks/klee

lahiri.phdworks

commit sha bf7c11ed7e49f13d7020bc1fb40377b465258e9f

TrueState & FalseState Cond Dumped

view details

push time in a month

push eventlahiri-phdworks/klee

lahiri.phdworks

commit sha cc91031fe47a8a9f736dee3bda4b5bc2c4b6d6c5

S-Expr Parsing Started

view details

push time in a month

push eventlahiri-phdworks/klee

push time in a month

push eventlahiri-phdworks/klee

Sumit Lahiri

commit sha 6ef22d29eca39ee6202f392dabdb637d94c2ebb4

Resolved PR

view details

push time in a month

PR merged lahiri-phdworks/klee

Update from KLEE:Master

Thank you for contributing to KLEE. We are looking forward to reviewing your PR. However, given the small number of active reviewers and our limited time, it might take a while to do so. We aim to get back to each PR within one month, and often do so within one week.

To help expedite the review please ensure the following, by adding an "x" for each completed item:

  • [ ] The PR addresses a single issue. In other words, if some parts of a PR could form another independent PR, you should break this PR into multiple smaller PRs.
  • [ ] There are no unnecessary commits. For instance, commits that fix issues with a previous commit in this PR are unnecessary and should be removed (you can find documentation on squashing commits here).
  • [ ] Larger PRs are divided into a logical sequence of commits.
  • [ ] Each commit has a meaningful message documenting what it does.
  • [ ] The code is commented. In particular, newly added classes and functions should be documented.
  • [ ] The patch is formatted via clang-format (see also git-clang-format for Git integration). Please only format the patch itself and code surrounding the patch, not entire files. Divergences from clang-formatting are only rarely accepted, and only if they clearly improve code readability.
  • [ ] Add test cases exercising the code you added or modified. We expect system and/or unit test cases for all non-trivial changes. After you submit your PR, you will be able to see a Codecov report telling you which parts of your patch are not covered by the regression test suite. You will also be able to see if the Github Actions CI and Cirrus CI tests have passed. If they don't, you should examine the failures and address them before the PR can be reviewed.
  • [ ] Spellcheck all messages added to the codebase, all comments, as well as commit messages.
+97 -51

0 comment

9 changed files

lahiri-phdworks

pr closed time in a month

push eventlahiri-phdworks/klee

Julian Büning

commit sha a9184832f238d1753667173a113bae7a5cfbe159

fix cflags for runtime build types - `-DNDebug` -> `-DNDEBUG` - different flags for `Release{+Debug,}+Asserts` - `-g` is no longer part of common flags - `-D_DEBUG` is now only set for debug builds - removed unused `LIB_BC_FLAGS_{32,64}` - added example, architecture prefix for specific flags

view details

Julian Büning

commit sha 5a194aa99fe2a13857dad2a5a5113b5856f8001d

retire some build system legacy

view details

Frank Busse

commit sha 302fae71de57d368505071637b3b0de539cf296b

posix runtime: remove dead branch

view details

Frank Busse

commit sha b605851ac60827687b1f48fbd3971703de555654

klee-libc: simplify mempcpy

view details

Frank Busse

commit sha 4ea592d293152d708ce678952c516d8ecae75ff1

klee.h: fix compiler warnings (function declaration is not a prototype)

view details

Frank Busse

commit sha bb6d9441d15e7205eb64ac4f53a2652940df180e

tests: add getcwd EINVAL test

view details

Frank Busse

commit sha b73c455670c467539a28611be8d30ac421be8441

posix runtime: getcwd: check malloc and set errno * failing malloc was not handled before, now returns null/ENOMEM * when path is non-null and size is zero return null/EINVAL

view details

Sumit Lahiri

commit sha d22c14b6b979a9453844a8c9d8e53a49d7769f73

Updates

view details

Sumit Lahiri

commit sha ded9ff84d0754ca6166a2938ac0012e56cbc171b

Merge branch 'new_patch' into symbolic_tree

view details

push time in a month

PullRequestEvent

PR closed lahiri-phdworks/klee

Update from KLEE:Master

Thank you for contributing to KLEE. We are looking forward to reviewing your PR. However, given the small number of active reviewers and our limited time, it might take a while to do so. We aim to get back to each PR within one month, and often do so within one week.

To help expedite the review please ensure the following, by adding an "x" for each completed item:

  • [ ] The PR addresses a single issue. In other words, if some parts of a PR could form another independent PR, you should break this PR into multiple smaller PRs.
  • [ ] There are no unnecessary commits. For instance, commits that fix issues with a previous commit in this PR are unnecessary and should be removed (you can find documentation on squashing commits here).
  • [ ] Larger PRs are divided into a logical sequence of commits.
  • [ ] Each commit has a meaningful message documenting what it does.
  • [ ] The code is commented. In particular, newly added classes and functions should be documented.
  • [ ] The patch is formatted via clang-format (see also git-clang-format for Git integration). Please only format the patch itself and code surrounding the patch, not entire files. Divergences from clang-formatting are only rarely accepted, and only if they clearly improve code readability.
  • [ ] Add test cases exercising the code you added or modified. We expect system and/or unit test cases for all non-trivial changes. After you submit your PR, you will be able to see a Codecov report telling you which parts of your patch are not covered by the regression test suite. You will also be able to see if the Github Actions CI and Cirrus CI tests have passed. If they don't, you should examine the failures and address them before the PR can be reviewed.
  • [ ] Spellcheck all messages added to the codebase, all comments, as well as commit messages.
+97 -51

0 comment

9 changed files

lahiri-phdworks

pr closed time in a month

push eventlahiri-phdworks/klee

Sumit Lahiri

commit sha 74b324b72b978f862317c3eccde802774c84aa7e

Updated Master

view details

push time in a month

push eventlahiri-phdworks/klee

Sumit Lahiri

commit sha 34f20bc76b0beefefbdc17b034077c5be3ee5cd2

Conditions Dumped

view details

push time in a month

push eventlahiri-phdworks/klee

Frank Busse

commit sha 302fae71de57d368505071637b3b0de539cf296b

posix runtime: remove dead branch

view details

Frank Busse

commit sha b605851ac60827687b1f48fbd3971703de555654

klee-libc: simplify mempcpy

view details

Frank Busse

commit sha 4ea592d293152d708ce678952c516d8ecae75ff1

klee.h: fix compiler warnings (function declaration is not a prototype)

view details

Frank Busse

commit sha bb6d9441d15e7205eb64ac4f53a2652940df180e

tests: add getcwd EINVAL test

view details

Frank Busse

commit sha b73c455670c467539a28611be8d30ac421be8441

posix runtime: getcwd: check malloc and set errno * failing malloc was not handled before, now returns null/ENOMEM * when path is non-null and size is zero return null/EINVAL

view details

Sumit Lahiri

commit sha 63b7b3335f6ae1f3fa53dd6aeb3c7cd9aaefe934

Merge pull request #19 from klee/master Update from KLEE Master

view details

push time in a month

PR merged lahiri-phdworks/klee

Update from KLEE Master

Thank you for contributing to KLEE. We are looking forward to reviewing your PR. However, given the small number of active reviewers and our limited time, it might take a while to do so. We aim to get back to each PR within one month, and often do so within one week.

To help expedite the review please ensure the following, by adding an "x" for each completed item:

  • [ ] The PR addresses a single issue. In other words, if some parts of a PR could form another independent PR, you should break this PR into multiple smaller PRs.
  • [ ] There are no unnecessary commits. For instance, commits that fix issues with a previous commit in this PR are unnecessary and should be removed (you can find documentation on squashing commits here).
  • [ ] Larger PRs are divided into a logical sequence of commits.
  • [ ] Each commit has a meaningful message documenting what it does.
  • [ ] The code is commented. In particular, newly added classes and functions should be documented.
  • [ ] The patch is formatted via clang-format (see also git-clang-format for Git integration). Please only format the patch itself and code surrounding the patch, not entire files. Divergences from clang-formatting are only rarely accepted, and only if they clearly improve code readability.
  • [ ] Add test cases exercising the code you added or modified. We expect system and/or unit test cases for all non-trivial changes. After you submit your PR, you will be able to see a Codecov report telling you which parts of your patch are not covered by the regression test suite. You will also be able to see if the Github Actions CI and Cirrus CI tests have passed. If they don't, you should examine the failures and address them before the PR can be reviewed.
  • [ ] Spellcheck all messages added to the codebase, all comments, as well as commit messages.
+86 -24

0 comment

6 changed files

lahiri-phdworks

pr closed time in a month

PR opened lahiri-phdworks/klee

Update from KLEE Master

Thank you for contributing to KLEE. We are looking forward to reviewing your PR. However, given the small number of active reviewers and our limited time, it might take a while to do so. We aim to get back to each PR within one month, and often do so within one week.

To help expedite the review please ensure the following, by adding an "x" for each completed item:

  • [ ] The PR addresses a single issue. In other words, if some parts of a PR could form another independent PR, you should break this PR into multiple smaller PRs.
  • [ ] There are no unnecessary commits. For instance, commits that fix issues with a previous commit in this PR are unnecessary and should be removed (you can find documentation on squashing commits here).
  • [ ] Larger PRs are divided into a logical sequence of commits.
  • [ ] Each commit has a meaningful message documenting what it does.
  • [ ] The code is commented. In particular, newly added classes and functions should be documented.
  • [ ] The patch is formatted via clang-format (see also git-clang-format for Git integration). Please only format the patch itself and code surrounding the patch, not entire files. Divergences from clang-formatting are only rarely accepted, and only if they clearly improve code readability.
  • [ ] Add test cases exercising the code you added or modified. We expect system and/or unit test cases for all non-trivial changes. After you submit your PR, you will be able to see a Codecov report telling you which parts of your patch are not covered by the regression test suite. You will also be able to see if the Github Actions CI and Cirrus CI tests have passed. If they don't, you should examine the failures and address them before the PR can be reviewed.
  • [ ] Spellcheck all messages added to the codebase, all comments, as well as commit messages.
+86 -24

0 comment

6 changed files

pr created time in a month

PR opened lahiri-phdworks/klee

Update from KLEE:Master

Thank you for contributing to KLEE. We are looking forward to reviewing your PR. However, given the small number of active reviewers and our limited time, it might take a while to do so. We aim to get back to each PR within one month, and often do so within one week.

To help expedite the review please ensure the following, by adding an "x" for each completed item:

  • [ ] The PR addresses a single issue. In other words, if some parts of a PR could form another independent PR, you should break this PR into multiple smaller PRs.
  • [ ] There are no unnecessary commits. For instance, commits that fix issues with a previous commit in this PR are unnecessary and should be removed (you can find documentation on squashing commits here).
  • [ ] Larger PRs are divided into a logical sequence of commits.
  • [ ] Each commit has a meaningful message documenting what it does.
  • [ ] The code is commented. In particular, newly added classes and functions should be documented.
  • [ ] The patch is formatted via clang-format (see also git-clang-format for Git integration). Please only format the patch itself and code surrounding the patch, not entire files. Divergences from clang-formatting are only rarely accepted, and only if they clearly improve code readability.
  • [ ] Add test cases exercising the code you added or modified. We expect system and/or unit test cases for all non-trivial changes. After you submit your PR, you will be able to see a Codecov report telling you which parts of your patch are not covered by the regression test suite. You will also be able to see if the Github Actions CI and Cirrus CI tests have passed. If they don't, you should examine the failures and address them before the PR can be reviewed.
  • [ ] Spellcheck all messages added to the codebase, all comments, as well as commit messages.
+11 -27

0 comment

3 changed files

pr created time in a month

push eventlahiri-phdworks/klee

Julian Büning

commit sha a9184832f238d1753667173a113bae7a5cfbe159

fix cflags for runtime build types - `-DNDebug` -> `-DNDEBUG` - different flags for `Release{+Debug,}+Asserts` - `-g` is no longer part of common flags - `-D_DEBUG` is now only set for debug builds - removed unused `LIB_BC_FLAGS_{32,64}` - added example, architecture prefix for specific flags

view details

Julian Büning

commit sha 5a194aa99fe2a13857dad2a5a5113b5856f8001d

retire some build system legacy

view details

Sumit Lahiri

commit sha 458a57842a57cc739b6a46e716e2b90c3d70dd2f

Merge pull request #17 from klee/master Update from KLEE:Master

view details

push time in a month

PR merged lahiri-phdworks/klee

Update from KLEE:Master

Thank you for contributing to KLEE. We are looking forward to reviewing your PR. However, given the small number of active reviewers and our limited time, it might take a while to do so. We aim to get back to each PR within one month, and often do so within one week.

To help expedite the review please ensure the following, by adding an "x" for each completed item:

  • [ ] The PR addresses a single issue. In other words, if some parts of a PR could form another independent PR, you should break this PR into multiple smaller PRs.
  • [ ] There are no unnecessary commits. For instance, commits that fix issues with a previous commit in this PR are unnecessary and should be removed (you can find documentation on squashing commits here).
  • [ ] Larger PRs are divided into a logical sequence of commits.
  • [ ] Each commit has a meaningful message documenting what it does.
  • [ ] The code is commented. In particular, newly added classes and functions should be documented.
  • [ ] The patch is formatted via clang-format (see also git-clang-format for Git integration). Please only format the patch itself and code surrounding the patch, not entire files. Divergences from clang-formatting are only rarely accepted, and only if they clearly improve code readability.
  • [ ] Add test cases exercising the code you added or modified. We expect system and/or unit test cases for all non-trivial changes. After you submit your PR, you will be able to see a Codecov report telling you which parts of your patch are not covered by the regression test suite. You will also be able to see if the Github Actions CI and Cirrus CI tests have passed. If they don't, you should examine the failures and address them before the PR can be reviewed.
  • [ ] Spellcheck all messages added to the codebase, all comments, as well as commit messages.
+11 -27

0 comment

3 changed files

lahiri-phdworks

pr closed time in a month

PR opened lahiri-phdworks/klee

Update from KLEE:Master

Thank you for contributing to KLEE. We are looking forward to reviewing your PR. However, given the small number of active reviewers and our limited time, it might take a while to do so. We aim to get back to each PR within one month, and often do so within one week.

To help expedite the review please ensure the following, by adding an "x" for each completed item:

  • [ ] The PR addresses a single issue. In other words, if some parts of a PR could form another independent PR, you should break this PR into multiple smaller PRs.
  • [ ] There are no unnecessary commits. For instance, commits that fix issues with a previous commit in this PR are unnecessary and should be removed (you can find documentation on squashing commits here).
  • [ ] Larger PRs are divided into a logical sequence of commits.
  • [ ] Each commit has a meaningful message documenting what it does.
  • [ ] The code is commented. In particular, newly added classes and functions should be documented.
  • [ ] The patch is formatted via clang-format (see also git-clang-format for Git integration). Please only format the patch itself and code surrounding the patch, not entire files. Divergences from clang-formatting are only rarely accepted, and only if they clearly improve code readability.
  • [ ] Add test cases exercising the code you added or modified. We expect system and/or unit test cases for all non-trivial changes. After you submit your PR, you will be able to see a Codecov report telling you which parts of your patch are not covered by the regression test suite. You will also be able to see if the Github Actions CI and Cirrus CI tests have passed. If they don't, you should examine the failures and address them before the PR can be reviewed.
  • [ ] Spellcheck all messages added to the codebase, all comments, as well as commit messages.
+11 -27

0 comment

3 changed files

pr created time in a month

issue commentaclements/latexrun

biblatex with biber only generated correctly on first run

It appears that the issue is fixed for me if I make the change proposed in this PR. It seems that latexrun doesn't account for the .bcf file output by biber, and so thinks the bibtex generation is done before it actually is. The linked PR fixes that.

languitar

comment created time in a month

push eventlahiri-phdworks/klee

Sumit Lahiri

commit sha 224da35b7403ee408b9c2491faf2eecd1a1eed82

Merge pull request #5 from klee/master Update from KLEE Master

view details

Sumit Lahiri

commit sha 90f3c41ff062e652a28e7cea5daee556f1cca6bb

Merge pull request #7 from klee/master Update from KLEE::master

view details

Sumit Lahiri

commit sha 85ba0ee825908c89c618ec3f280ac80b31f16ad9

Merge pull request #9 from klee/master fix Executor: remove UB from bindInstructionConstants

view details

Sumit Lahiri

commit sha be28236bdfdd4c0c09ab1210971dd10a0e2530f9

Merge pull request #11 from klee/master Update from KLEE:master

view details

Sumit Lahiri

commit sha 64fc8352b9aacfced58211d6fb84affda9b5663f

Merge pull request #14 from klee/master Update master from KLEE:master

view details

Julian Büning

commit sha 4d548131c1ac079719a26b37867a6b18ba65cee1

fix CMake: libcxxabi is only required with KLEE_EH_CXX

view details

Julian Büning

commit sha e7fd8c10f03c99a373eb800cf03ba019dc35f81a

slightly improve C++-related CMake strings

view details

Julian Büning

commit sha e2f65b57afefa979382062c149fac55eae76e513

p-klee.inc: libc++abi only needed for c++ exception support

view details

Cristian Cadar

commit sha 53ace1a119c5ede520d2e597f9bcdfeece31229a

Use a more recent version of macOS

view details

Martin Nowack

commit sha d83484b63c089281a32e3d3fb8b59b21a3eb7d79

Use non-interactive input

view details

Martin Nowack

commit sha 26b13da1c032ff3426012f43b17a8fa86598857b

Handle LLVM version selection more robust

view details

Martin Nowack

commit sha d450b92e6faa361dae7f425e285b42b6792691d0

Detect system include headers on macOS System header files on macOS are not part of `/usr/include` since Catalina. Instead, multiple locations are possible and depend on the selected SDK. Use `xcrun` to automatically detect the correct path on macOS.

view details

Martin Nowack

commit sha 96ce9feee0c05275cc2dae9fb0e2f9f42b035c91

Add Github Actions for KLEE CI based @jordr Add support for Github Actions to use as new CI. This builds all the components as the original Travis CI script.

view details

Martin Nowack

commit sha 8a9c2db6e32e813a780eeb759d310bb883ed1152

Rename `build-travis-container.py` into `build-ci-container.py` Update container build script to utilize Github Actions job description instead of Travis CI's.

view details

Martin Nowack

commit sha 4411278ed77bda7d51edd0cbae160b1cdaa0e7b9

Remove artificial timeouts as current timeout for build jobs is 6h.

view details

Martin Nowack

commit sha c51ffcd377097ee80ec9b0d6f07f8ea583a5aa1d

Use Github Actions as default CI

view details

Martin Nowack

commit sha 729825e1c80eb6a21441fa4d55c967549e231e1f

Fix Codecov upload `sudo` invocation in Github Actions does not provide environment variables, therefore Codecov was not aware of the correct settings. This behaviour is different under Github Actions than Travis CI. This could be fixed via `sudo -E`. Anyway, tests do not need to be run `sudo` with Github Actions, so remove the `sudo` invocation in the first place.

view details

Cristian Cadar

commit sha fba9ea939e333df3db40091c6c9825f4f5485acb

Declare mempcpy on macOS, to silence compiler warnings

view details

Cristian Cadar

commit sha 549206763cab1154fe05fc7a9a5f0e089405dcbd

Add LLVM 11 to lit.cfg

view details

Cristian Cadar

commit sha 9be3e76ed1f9eb0ec86531e2437091f7f1f02c88

Move all overflows from the vector instructions tests into a new file, as the overflow behaviour is different in LLVM 11.

view details

push time in a month

more