Issue 33312 in oss-fuzz: binutils: Fuzzing build failure

2021-04-17 Thread p . ant… via monorail
Comment #4 on issue 33312 by p.ant...@catenacyber.fr: binutils: Fuzzing build failure https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=33312#c4 https://github.com/google/oss-fuzz/pull/5628 -- You received this message because: 1. You were specifically CC'd on the issue You may adjust y

Issue 33312 in oss-fuzz: binutils: Fuzzing build failure

2021-04-16 Thread amo… via monorail
Comment #3 on issue 33312 by amo...@gmail.com: binutils: Fuzzing build failure https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=33312#c3 Yes exactly, and I'm not going to pollute the binutils source with #ifdef around those functions. There are plenty of other static inline functions defi

Issue 33312 in oss-fuzz: binutils: Fuzzing build failure

2021-04-16 Thread p . ant… via monorail
Comment #2 on issue 33312 by p.ant...@catenacyber.fr: binutils: Fuzzing build failure https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=33312#c2 It looks like get_stat_mtime_ns is defined in all cases but used only with certain #ifdef conditions -- You received this message because: 1.

Issue 33312 in oss-fuzz: binutils: Fuzzing build failure

2021-04-16 Thread amo… via monorail
Comment #1 on issue 33312 by amo...@gmail.com: binutils: Fuzzing build failure https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=33312#c1 clang warns about two unused "static inline" functions. Really? -- You received this message because: 1. You were specifically CC'd on the issue You