public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/105252] New: [12 Regression] ICE: in cmp_cst, at analyzer/svalue.cc:309 with -O -fanalyzer -fnon-call-exceptions
Date: Wed, 13 Apr 2022 04:33:30 +0000	[thread overview]
Message-ID: <bug-105252-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105252

            Bug ID: 105252
           Summary: [12 Regression] ICE: in cmp_cst, at
                    analyzer/svalue.cc:309 with -O -fanalyzer
                    -fnon-call-exceptions
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: analyzer
          Assignee: dmalcolm at gcc dot gnu.org
          Reporter: zsojka at seznam dot cz
  Target Milestone: ---
              Host: x86_64-pc-linux-gnu

Created attachment 52793
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52793&action=edit
reduced testcase

Compiler output:
$ x86_64-pc-linux-gnu-gcc -O -fanalyzer -fnon-call-exceptions testcase.c 
during IPA pass: analyzer
In function 'bar',
    inlined from 'foo' at testcase.c:17:3:
testcase.c:9:5: internal compiler error: in cmp_cst, at analyzer/svalue.cc:309
    9 |   v %= (c | v) % m;
      |     ^~
0x82fef8 cmp_cst
        /repo/gcc-trunk/gcc/analyzer/svalue.cc:309
0x17a8abf cmp_cst
        /repo/gcc-trunk/gcc/analyzer/svalue.cc:340
0x17a8f03 ana::svalue::cmp_ptr(ana::svalue const*, ana::svalue const*)
        /repo/gcc-trunk/gcc/analyzer/svalue.cc:428
0x2543d40 cmp1<sort_ctx>
        /repo/gcc-trunk/gcc/sort.cc:153
0x2543d94 netsort<sort_ctx>
        /repo/gcc-trunk/gcc/sort.cc:170
0x2543d94 mergesort<sort_ctx>
        /repo/gcc-trunk/gcc/sort.cc:207
0x254431f gcc_qsort(void*, unsigned long, unsigned long, int (*)(void const*,
void const*))
        /repo/gcc-trunk/gcc/sort.cc:266
0x17417ed vec<ana::svalue const*, va_heap, vl_embed>::qsort(int (*)(void
const*, void const*))
        /repo/gcc-trunk/gcc/vec.h:1147
0x17417ed vec<ana::svalue const*, va_heap, vl_ptr>::qsort(int (*)(void const*,
void const*))
        /repo/gcc-trunk/gcc/vec.h:2121
0x17417ed ana::program_state::detect_leaks(ana::program_state const&,
ana::program_state const&, ana::svalue const*, ana::extrinsic_state const&,
ana::region_model_context*)
        /repo/gcc-trunk/gcc/analyzer/program-state.cc:1420
0x1741b66 ana::program_state::prune_for_point(ana::exploded_graph&,
ana::program_point const&, ana::exploded_node*, ana::uncertainty_t*) const
        /repo/gcc-trunk/gcc/analyzer/program-state.cc:1214
0x172f78f ana::exploded_graph::process_node(ana::exploded_node*)
        /repo/gcc-trunk/gcc/analyzer/engine.cc:3780
0x1730622 ana::exploded_graph::process_worklist()
        /repo/gcc-trunk/gcc/analyzer/engine.cc:3198
0x1732b27 ana::impl_run_checkers(ana::logger*)
        /repo/gcc-trunk/gcc/analyzer/engine.cc:5777
0x17339be ana::run_checkers()
        /repo/gcc-trunk/gcc/analyzer/engine.cc:5851
0x1722f48 execute
        /repo/gcc-trunk/gcc/analyzer/analyzer-pass.cc:87
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.

$ x86_64-pc-linux-gnu-gcc -v
Using built-in specs.
COLLECT_GCC=/repo/gcc-trunk/binary-latest-amd64/bin/x86_64-pc-linux-gnu-gcc
COLLECT_LTO_WRAPPER=/repo/gcc-trunk/binary-trunk-r12-8113-20220412190241-gaa7874596b9-checking-yes-rtl-df-extra-amd64/bin/../libexec/gcc/x86_64-pc-linux-gnu/12.0.1/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: /repo/gcc-trunk//configure --enable-languages=c,c++
--enable-valgrind-annotations --disable-nls --enable-checking=yes,rtl,df,extra
--with-cloog --with-ppl --with-isl --build=x86_64-pc-linux-gnu
--host=x86_64-pc-linux-gnu --target=x86_64-pc-linux-gnu
--with-ld=/usr/bin/x86_64-pc-linux-gnu-ld
--with-as=/usr/bin/x86_64-pc-linux-gnu-as --disable-libstdcxx-pch
--prefix=/repo/gcc-trunk//binary-trunk-r12-8113-20220412190241-gaa7874596b9-checking-yes-rtl-df-extra-amd64
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 12.0.1 20220412 (experimental) (GCC)

             reply	other threads:[~2022-04-13  4:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-13  4:33 zsojka at seznam dot cz [this message]
2022-04-13  6:56 ` [Bug analyzer/105252] " rguenth at gcc dot gnu.org
2022-04-13  7:53 ` [Bug analyzer/105252] [12 Regression] ICE: in cmp_cst, at analyzer/svalue.cc:309 with -O -fanalyzer -fnon-call-exceptions since r12-1931-ge61ffa201403e381 marxin at gcc dot gnu.org
2022-04-13 16:20 ` dmalcolm at gcc dot gnu.org
2022-04-14 12:51 ` cvs-commit at gcc dot gnu.org
2022-04-14 13:03 ` dmalcolm at gcc dot gnu.org
2022-04-28 21:42 ` cvs-commit 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-105252-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).