[Bug sanitizer/91101] Possible performance regression in libasan with detect_stack_use_after_return=1
marxin at gcc dot gnu.org
gcc-bugzilla@gcc.gnu.org
Mon Jul 8 08:01:00 GMT 2019
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91101
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2019-07-08
Ever confirmed|0 |1
--- Comment #4 from Martin Liška <marxin at gcc dot gnu.org> ---
Ok, I was able to make the build:
$ meson build -Db_sanitize=address,undefined -Dxkbcommon=false
with GCC 9.1.1:
$ time ./build/test-conf-parser
filename:1: lvalue= path is not absolute, ignoring: not_absolute/path
filename:1: String is not UTF-8 clean, ignoring assignment: /path/�
filename:1: Failed to parse log level, ignoring: garbage
filename:1: Failed to parse log facility, ignoring: garbage
filename:1: Failed to parse size value '-982', ignoring: Numerical result out
of range
filename:1: Failed to parse size value '49874444198739873000000G', ignoring:
Numerical result out of range
filename:1: Failed to parse size value 'garbage', ignoring: Invalid argument
filename:1: Failed to parse size value '-982', ignoring: Numerical result out
of range
filename:1: Failed to parse size value '49874444198739873000000G', ignoring:
Numerical result out of range
filename:1: Failed to parse size value 'garbage', ignoring: Invalid argument
filename:1: Failed to parse int value, ignoring:
99999999999999999999999999999999999999999999999999999999
filename:1: Failed to parse int value, ignoring:
-99999999999999999999999999999999999999999999999999999999
filename:1: Failed to parse int value, ignoring: 1G
filename:1: Failed to parse int value, ignoring: garbage
filename:1: Failed to parse unsigned value, ignoring:
99999999999999999999999999999999999999999999999999999999
filename:1: Failed to parse unsigned value, ignoring: 1G
filename:1: Failed to parse unsigned value, ignoring: garbage
filename:1: Failed to parse unsigned value, ignoring: 1000garbage
filename:1: Failed to parse mode value, ignoring: -777
filename:1: Failed to parse mode value, ignoring: 999
filename:1: Failed to parse mode value, ignoring: garbage
filename:1: Failed to parse mode value, ignoring: 777garbage
filename:1: Failed to parse mode value, ignoring: 777 garbage
filename:1: Failed to parse sec value, ignoring: -1
filename:1: Failed to parse sec value, ignoring: 10foo
filename:1: Failed to parse sec value, ignoring: garbage
filename:1: Failed to parse nsec value, ignoring: -1
filename:1: Failed to parse nsec value, ignoring: 10foo
filename:1: Failed to parse nsec value, ignoring: garbage
== test_config_parse[0] ==
== test_config_parse[1] ==
== test_config_parse[2] ==
== test_config_parse[3] ==
== test_config_parse[4] ==
== test_config_parse[5] ==
== test_config_parse[6] ==
== test_config_parse[7] ==
== test_config_parse[8] ==
== test_config_parse[9] ==
== test_config_parse[10] ==
== test_config_parse[11] ==
== test_config_parse[12] ==
== test_config_parse[13] ==
== test_config_parse[14] ==
== test_config_parse[15] ==
/tmp/test-conf-parser.l7EgI7:1: Line too long
== test_config_parse[16] ==
/tmp/test-conf-parser.2Fj9TE:1: Continuation line too long
real 0m2.176s
user 0m2.013s
sys 0m0.160s
which is probably fast enough. And I can't run the second test-case:
$ ./test/hwdb-test.sh
./systemd-hwdb does not exist, please build first
More information about the Gcc-bugs
mailing list