Nikita Popov
Nikita Popov
Parsing the input `@\Afffff` produces an "illegal character" warning from iconv. Possibly this just needs to be suppressed or converted into an exception? ``` #1 /home/nikic/PHP-Fuzzer/example/PHP-CSS-Parser/lib/Sabberworm/CSS/Parsing/ParserState.php(96): iconv('utf-32le', 'utf-8', '\xFF\xFF\xAF\x00') #2...
Parsing the input `a{f:#1` produces an uninitialized string offset warning: ``` Error: [2] Uninitialized string offset: 1 in /home/nikic/PHP-Fuzzer/example/PHP-CSS-Parser/lib/Sabberworm/CSS/Value/Color.php on line 33 in /home/nikic/PHP-Fuzzer/src/Fuzzer.php:471 Stack trace: #0 /home/nikic/PHP-Fuzzer/example/PHP-CSS-Parser/lib/Sabberworm/CSS/Value/Color.php(33): PhpFuzzer\Fuzzer->PhpFuzzer\{closure}(2, 'Uninitialized...
When trying to parse the input `P{P:[`, the parser goes into an infinite loop. Backtrace snapshot: ``` #1 /home/nikic/PHP-Fuzzer/example/PHP-CSS-Parser/lib/Sabberworm/CSS/Parsing/ParserState.php(52): Sabberworm\CSS\Parsing\ParserState->parseCharacter(true) #2 /home/nikic/PHP-Fuzzer/example/PHP-CSS-Parser/lib/Sabberworm/CSS/Value/LineName.php(20): Sabberworm\CSS\Parsing\ParserState->parseIdentifier() #3 /home/nikic/PHP-Fuzzer/example/PHP-CSS-Parser/lib/Sabberworm/CSS/Value/Value.php(94): Sabberworm\CSS\Value\LineName::parse(Object(Sabberworm\CSS\Parsing\ParserState)) #4 /home/nikic/PHP-Fuzzer/example/PHP-CSS-Parser/lib/Sabberworm/CSS/Value/Value.php(36): Sabberworm\CSS\Value\Value::parsePrimitiveValue(Object(Sabberworm\CSS\Parsing\ParserState)) #5...
Parsing the string `P{P/*` results in a TypeError: ``` TypeError: Argument 1 passed to Sabberworm\CSS\Rule\Rule::addComments() must be of the type array, null given, called in /home/nikic/PHP-Fuzzer/example/PHP-CSS-Parser/lib/Sabberworm/CSS/Rule/Rule.php on line 37 and...
Sometimes it is convenient to write a value to `out.member` and read and adjust it lateron. Right now this is not prohibited, but will not work correctly on all backends....
Currently step functions are executed strictly in order. However, it is possible to run step functions acting on different agent types in parallel, if there aren't any interdependencies. In FlameGPU...
Due to #11 library functions are included in the generated code, even if they are not used. It would be good to discard functions that are not used in the...
Right now the main() code is ignored, because Flame/FlameGPU don't have a good place where it can be run. Because of this it's currently necessary to generate the initial agent...
We can only replace phi(X, undef) with X, if X is known not to be poison. Otherwise, the result may be more poisonous on the undef branch.
These were never actually used, and the way they were constructed doesn't really make sense. Fixes https://github.com/llvm/llvm-project/issues/93798.