Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: google/effcee
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 4bef5dbed590
Choose a base ref
...
head repository: google/effcee
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 6527fb25482e
Choose a head ref
  • 4 commits
  • 9 files changed
  • 2 contributors

Commits on Aug 19, 2019

  1. Add Bazel build rules.

    This adds support for building effcee with Bazel (https://bazel.build).
    
    It automatically pulls the googletest and re2 repositories when building
    with Bazel.  I did not add a sha256 attribute to fix the version of the
    external repos to get, so by default this tracks top-of-master for those
    repos.
    
    It's easy to fix the versions by adding the sha256 attribute that Bazel
    suggests when it starts.
    dnovillo authored and dneto0 committed Aug 19, 2019
    Configuration menu
    Copy the full SHA
    3842fdc View commit details
    Browse the repository at this point in the history

Commits on Aug 24, 2019

  1. Add effcee-fuzz

    It's only built if you specify a CMake variable pointing
    at the FuzzedDataProvider.h source file from LLVM's compiler-rt.
    
    effcee-fuzz runs a simple matcher against standard input.
    This can be used to simply and easily reproduce OSS-Fuzz failures.
    dneto0 committed Aug 24, 2019
    Configuration menu
    Copy the full SHA
    ecbc165 View commit details
    Browse the repository at this point in the history
  2. Fail parsing checks if the regexp is bad.

    BUG=129514492
    dneto0 committed Aug 24, 2019
    Configuration menu
    Copy the full SHA
    0eb6499 View commit details
    Browse the repository at this point in the history

Commits on Aug 26, 2019

  1. Fail parsing checks if var def regexp is bad

    e.g. bad pattern [[FOO:?]]
    The question mark is a quantifier that doesn't quantify anything.
    
    BUG=137632977
    dneto0 committed Aug 26, 2019
    Configuration menu
    Copy the full SHA
    6527fb2 View commit details
    Browse the repository at this point in the history
Loading