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/113496] New: ICE: in cmp, at analyzer/constraint-manager.cc:782 with -fanalyzer -fdump-analyzer
Date: Fri, 19 Jan 2024 05:52:46 +0000	[thread overview]
Message-ID: <bug-113496-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 113496
           Summary: ICE: in cmp, at analyzer/constraint-manager.cc:782
                    with -fanalyzer -fdump-analyzer
           Product: gcc
           Version: 14.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
            Target: x86_64-pc-linux-gnu

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

Compiler output:
$ x86_64-pc-linux-gnu-gcc -fanalyzer -fdump-analyzer u_format_latc.c.i
u_format_latc.c.i: In function
'util_format_colormask_descutil_format_colormask':
u_format_latc.c.i:11:5: warning: infinite loop [CWE-835]
[-Wanalyzer-infinite-loop]
   11 |     case UTIL_FORMAT_COLORSPACE_ZS:;
      |     ^~~~
  'util_format_colormask_descutil_format_colormask': event 1
    |
    |   11 |     case UTIL_FORMAT_COLORSPACE_ZS:;
    |      |     ^~~~
    |      |     |
    |      |     (1) infinite loop here
    |
  'util_format_colormask_descutil_format_colormask': event 2
    |
    |cc1:
    | (2): looping back...
    |
  'util_format_colormask_descutil_format_colormask': event 3
    |
    |   11 |     case UTIL_FORMAT_COLORSPACE_ZS:;
    |      |     ^~~~
    |      |     |
    |      |     (3) ...to here
    |
during IPA pass: analyzer
At top level:
cc1: internal compiler error: in cmp, at analyzer/constraint-manager.cc:782
0xdd2429 ana::bounded_ranges::cmp(ana::bounded_ranges const*,
ana::bounded_ranges const*)
        /repo/gcc-trunk/gcc/analyzer/constraint-manager.cc:782
0xdd2429 ana::bounded_ranges::cmp(ana::bounded_ranges const*,
ana::bounded_ranges const*)
        /repo/gcc-trunk/gcc/analyzer/constraint-manager.cc:770
0x29fcbd8 cmp1<sort_ctx>
        /repo/gcc-trunk/gcc/sort.cc:151
0x29fcc31 netsort<sort_ctx>
        /repo/gcc-trunk/gcc/sort.cc:168
0x29fcc31 mergesort<sort_ctx>
        /repo/gcc-trunk/gcc/sort.cc:205
0x29fce7d mergesort<sort_ctx>
        /repo/gcc-trunk/gcc/sort.cc:212
0x29fd22f gcc_qsort(void*, unsigned long, unsigned long, int (*)(void const*,
void const*))
        /repo/gcc-trunk/gcc/sort.cc:268
0x291b316 vec<ana::bounded_ranges const*, va_heap, vl_embed>::qsort(int
(*)(void const*, void const*))
        /repo/gcc-trunk/gcc/vec.h:1217
0x291b316 vec<ana::bounded_ranges const*, va_heap, vl_ptr>::qsort(int (*)(void
const*, void const*))
        /repo/gcc-trunk/gcc/vec.h:2240
0x291b316 ana::bounded_ranges_manager::log_stats(ana::logger*, bool) const
        /repo/gcc-trunk/gcc/analyzer/constraint-manager.cc:1040
0x195f957 ana::region_model_manager::log_stats(ana::logger*, bool) const
        /repo/gcc-trunk/gcc/analyzer/region-model-manager.cc:1929
0x190fc1f ana::exploded_graph::log_stats() const
        /repo/gcc-trunk/gcc/analyzer/engine.cc:4551
0x19113f7 ana::impl_run_checkers(ana::logger*)
        /repo/gcc-trunk/gcc/analyzer/engine.cc:6230
0x191227b ana::run_checkers()
        /repo/gcc-trunk/gcc/analyzer/engine.cc:6300
0x1900f38 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-r14-8259-20240118193928-gb6c4fcda7fe-checking-yes-rtl-df-extra-nobootstrap-amd64/bin/../libexec/gcc/x86_64-pc-linux-gnu/14.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
--disable-bootstrap --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-r14-8259-20240118193928-gb6c4fcda7fe-checking-yes-rtl-df-extra-nobootstrap-amd64
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 14.0.1 20240118 (experimental) (GCC)

             reply	other threads:[~2024-01-19  5:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-19  5:52 zsojka at seznam dot cz [this message]
2024-02-15 17:41 ` [Bug analyzer/113496] [12/13/14 Regression] " dmalcolm at gcc dot gnu.org
2024-03-04 13:05 ` rguenth at gcc dot gnu.org
2024-03-07 20:48 ` law at gcc dot gnu.org
2024-03-12 13:21 ` 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-113496-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).