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] New: OVS compiled with gcc10 with -fanalyzer
Date: Mon, 13 Apr 2020 14:49:10 +0000 [thread overview]
Message-ID: <bug-94579-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94579
Bug ID: 94579
Summary: OVS compiled with gcc10 with -fanalyzer
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: u9012063 at gmail dot com
Target Milestone: ---
Hi,
I'd like to create an account to submit a bug for gcc10
when compiling openvswitch
$ uname -a
Linux osboxes 5.5.0-rc1+ #112 SMP Fri Feb 21 10:28:49 PST 2020 x86_64 x86_64
x86_64 GNU/L
$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc/x86_64-pc-linux-gnu/10.0.1/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ./configure
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 10.0.1 20200405 (experimental) (GCC)
$ git clone https://github.com/openvswitch/ovs.git
$ cd ovs
$ ./boot.sh; ./configure; make CFLAGS+=-fanalyzer
In file included from lib/flow.h:31,
from lib/flow.c:18:
lib/packets.h: In function ‘in6_addr_mapped_ipv4’:
lib/packets.h:1187:12: internal compiler error: in saved_diagnostic,
at analyzer/diagnostic-manager.cc:84
1187 | return ip6;
| ^~~
0x7888f9 ana::saved_diagnostic::saved_diagnostic(ana::state_machine
const*, ana::exploded_node const*, ana::supernode const*, gimple
const*, ana::stmt_finder*, tree_node*, unsigned int,
ana::pending_diagnostic*)
../.././gcc/analyzer/diagnostic-manager.cc:84
0x1757703 ana::diagnostic_manager::add_diagnostic(ana::state_machine
const*, ana::exploded_node const*, ana::supernode const*, gimple
const*, ana::stmt_finder*, tree_node*, unsigned int,
ana::pending_diagnostic*)
../.././gcc/analyzer/diagnostic-manager.cc:175
0x17578f9 ana::diagnostic_manager::add_diagnostic(ana::exploded_node
const*, ana::supernode const*, gimple const*, ana::stmt_finder*,
ana::pending_diagnostic*)
../.././gcc/analyzer/diagnostic-manager.cc:192
0x10aead4 ana::impl_region_model_context::warn(ana::pending_diagnostic*)
../.././gcc/analyzer/engine.cc:114
0x10d3664 ana::region_model::deref_rvalue(ana::svalue_id,
ana::region_model_context*)
../.././gcc/analyzer/region-model.cc:5458
0x10d59de ana::region_model::get_or_create_mem_ref(tree_node*,
ana::svalue_id, ana::svalue_id, ana::region_model_context*)
../.././gcc/analyzer/region-model.cc:6971
0x10d62b3 ana::region_model::get_lvalue(ana::path_var,
ana::region_model_context*)
../.././gcc/analyzer/region-model.cc:5068
0x10de90d ana::region_model::update_for_return_superedge(ana::return_superedge
const&, ana::region_model_context*)
../.././gcc/analyzer/region-model.cc:6171
0x10dea17 ana::region_model::maybe_update_for_edge(ana::superedge
const&, gimple const*, ana::region_model_context*)
../.././gcc/analyzer/region-model.cc:6092
0x10c37d2 ana::program_state::on_edge(ana::exploded_graph&,
ana::exploded_node const&, ana::superedge const*, ana::state_change*)
../.././gcc/analyzer/program-state.cc:829
0x10af589 ana::exploded_node::on_edge(ana::exploded_graph&,
ana::superedge const*, ana::program_point*, ana::program_state*,
ana::state_change*) const
../.././gcc/analyzer/engine.cc:1153
0x10b6b5b ana::exploded_graph::process_node(ana::exploded_node*)
../.././gcc/analyzer/engine.cc:2597
0x10b716a ana::exploded_graph::process_worklist()
../.././gcc/analyzer/engine.cc:2348
0x10b787b ana::impl_run_checkers(ana::logger*)
../.././gcc/analyzer/engine.cc:4029
0x10b840c ana::run_checkers()
../.././gcc/analyzer/engine.cc:4097
0x10ad598 execute
../.././gcc/analyzer/analyzer-pass.cc:84
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
next reply other threads:[~2020-04-13 14:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 14:49 u9012063 at gmail dot com [this message]
2020-04-13 14:52 ` [Bug c/94579] " u9012063 at gmail dot com
2020-04-13 14:54 ` u9012063 at gmail dot com
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@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).