public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "u9012063 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/94579] OVS compiled with gcc10 with -fanalyzer
Date: Mon, 13 Apr 2020 14:54:42 +0000 [thread overview]
Message-ID: <bug-94579-4-A9Yh3V5846@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94579-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94579
--- Comment #2 from William Tu <u9012063 at gmail dot com> ---
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I ./include -I ./include -I ./lib
-I ./lib -Wstrict-prototypes -Wall -Wextra -Wno-sign-compare -Wpointer-arith
-Wformat -Wformat-security -Wswitch-enum -Wunused-parameter -Wbad-function-cast
-Wcast-align -Wstrict-prototypes -Wold-style-definition -Wmissing-prototypes
-Wmissing-field-initializers -fno-strict-aliasing -Wswitch-bool
-Wlogical-not-parentheses -Wsizeof-array-argument -Wbool-compare
-Wshift-negative-value -Wduplicated-cond -Wshadow -Wmultistatement-macros
-Wcast-align=strict -fanalyzer -MT lib/flow.lo -MD -MP -MF lib/.deps/flow.Tpo
-c lib/flow.c -o lib/flow.o
during IPA pass: analyzer
In file included from lib/flow.h:31,
from lib/flow.c:18:
lib/packets.h: In function ‘in6_addr_mapped_ipv4’:
next prev parent reply other threads:[~2020-04-13 14:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 14:49 [Bug c/94579] New: " u9012063 at gmail dot com
2020-04-13 14:52 ` [Bug c/94579] " u9012063 at gmail dot com
2020-04-13 14:54 ` u9012063 at gmail dot com [this message]
2020-04-14 6:56 ` [Bug c/94579] OVS compiled with gcc10 with -fanalyzer since r10-7502-ga96f1c38a787fbc8 marxin at gcc dot gnu.org
2020-04-14 7:15 ` rguenth at gcc dot gnu.org
2020-08-17 5:08 ` asolokha at gmx dot com
2021-11-30 22:50 ` [Bug analyzer/94579] " cvs-commit at gcc dot gnu.org
2021-11-30 23:02 ` dmalcolm 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-94579-4-A9Yh3V5846@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: link
Be 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).