Compilation database project breaks if -std exists in the compilation arguments of a C source file

When using the CompilationDatabaseProjectManager plugin and opening a project from a compile_commands.json file, none of the C source files in it are recognized as part of the project if the first one of them contains an "-std=" option in "arguments". Example: 

[
    {
        "arguments": [
            "gcc",
            "-c",
            "-std=gnu99",
            "-o",
            "obj/test.o",
            "src/test.c"
        ],
        "directory": "/home/realnc/projects/CompDatabaseTest",
        "file": "src/test.c"
    }
]

It doesn't matter if I replace "gcc" with g+, clang or clang+. If it's a *.c file, the "-std" argument prevents Creator from being able to parse any of the C files correctly and a yellow icon appears at the top that says: "This file is not part of any project."

The problem doesn't exist with C++ sources. For example, this works fine: 

[
    {
        "arguments": [
            "g++",
            "-c",
            "-std=c++14",
            "-o",
            "obj/test.o",
            "src/test.cpp"
        ],
        "directory": "/home/realnc/projects/CompDatabaseTest",
        "file": "src/test.cpp"
    }
]