public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/64013] New: [5 Regression] libsanitizer fails to build Date: Fri, 21 Nov 2014 08:43:00 -0000 [thread overview] Message-ID: <bug-64013-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64013 Bug ID: 64013 Summary: [5 Regression] libsanitizer fails to build Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: rguenth at gcc dot gnu.org CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org, jakub at gcc dot gnu.org, kcc at gcc dot gnu.org [35101s] I: Program returns random data in a function [35101s] E: gcc5 no-return-in-nonvoid-function ../../../../libsanitizer/sanitizer_common/sanitizer_linux.cc:295 bool FileExists(const char *filename) { #if SANITIZER_USES_CANONICAL_LINUX_SYSCALLS struct stat st; if (internal_syscall(SYSCALL(newfstatat), AT_FDCWD, filename, &st, 0)) return false; #else struct stat st; if (internal_stat(filename, &st)) return false; // Sanity check: filename is a regular file. return S_ISREG(st.st_mode); #endif } the SANITIZER_USES_CANONICAL_LINUX_SYSCALLS misses a return.
next reply other threads:[~2014-11-21 8:43 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-11-21 8:43 rguenth at gcc dot gnu.org [this message] 2014-11-21 8:43 ` [Bug sanitizer/64013] " rguenth at gcc dot gnu.org 2014-11-21 8:47 ` rguenth at gcc dot gnu.org 2014-11-21 13:46 ` jakub at gcc dot gnu.org 2014-11-21 13:56 ` dvyukov at google dot com 2014-11-21 14:04 ` jakub at gcc dot gnu.org 2014-11-24 9:04 ` jakub at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-64013-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).