public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/107898] New: [11/12/13 Regression] ICE in irange_intersect, at value-range.cc:1640 Date: Mon, 28 Nov 2022 17:58:51 +0000 [thread overview] Message-ID: <bug-107898-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107898 Bug ID: 107898 Summary: [11/12/13 Regression] ICE in irange_intersect, at value-range.cc:1640 Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: gscfq@t-online.de Target Milestone: --- Started between 20220403 and 20220410, with file gcc.dg/Walloca-larger-than-2.c : (and started between 20201018 and 20201108 with -O1+) $ gcc-13-20221127 -c Walloca-larger-than-2.c -fsanitize=address -fsanitize=pointer-subtract -fpreprocessed -Walloca-larger-than=5000 Walloca-larger-than-2.c:7:1: warning: parameter names (without types) in function declaration 7 | extern void* alloca (__SIZE_TYPE__); | ^~~~~~ Walloca-larger-than-2.c: In function 'test_alloca': Walloca-larger-than-2.c:17:5: warning: implicit declaration of function 'T' [-Wimplicit-function-declaration] 17 | T (alloca (0)); | ^ Walloca-larger-than-2.c:17:16: warning: 'alloca' argument 1 type is 'int' where 'long unsigned int' is expected in a call to built-in function declared without prototype [-Wbuiltin-declaration-mismatch] 17 | T (alloca (0)); | ^ Walloca-larger-than-2.c:7:14: note: built-in 'alloca' declared here 7 | extern void* alloca (__SIZE_TYPE__); | ^~~~~~ Walloca-larger-than-2.c:21:16: warning: 'alloca' argument 1 type is 'int' where 'long unsigned int' is expected in a call to built-in function declared without prototype [-Wbuiltin-declaration-mismatch] 21 | T (alloca (1)); | ^ Walloca-larger-than-2.c:7:14: note: built-in 'alloca' declared here 7 | extern void* alloca (__SIZE_TYPE__); | ^~~~~~ Walloca-larger-than-2.c:24:16: warning: 'alloca' argument 1 type is 'unsigned int' where 'long unsigned int' is expected in a call to built-in function declared without prototype [-Wbuiltin-declaration-mismatch] 24 | T (alloca (n)); | ^ Walloca-larger-than-2.c:7:14: note: built-in 'alloca' declared here 7 | extern void* alloca (__SIZE_TYPE__); | ^~~~~~ Walloca-larger-than-2.c:17:5: warning: argument to 'alloca' is zero [-Walloca-larger-than=] 17 | T (alloca (0)); | ^~~~~~~~~~~~~~ Walloca-larger-than-2.c:21:5: warning: use of 'alloca' within a loop [-Walloca-larger-than=] 21 | T (alloca (1)); | ^~~~~~~~~~~~~~ during GIMPLE pass: walloca Walloca-larger-than-2.c:25:1: internal compiler error: in irange_intersect, at value-range.cc:2560 25 | } | ^ 0x12550c8 irange::irange_intersect(irange const&) ../../gcc/value-range.cc:2559 0x1251a81 irange::legacy_verbose_intersect(irange const*) ../../gcc/value-range.cc:2324 0x1cc78dc irange::intersect(vrange const&) ../../gcc/value-range.h:969 0x1cc78dc alloca_call_type ../../gcc/gimple-ssa-warn-alloca.cc:228 0x1cc8243 pass_walloca::execute(function*) ../../gcc/gimple-ssa-warn-alloca.cc:292
next reply other threads:[~2022-11-28 17:58 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-28 17:58 gscfq@t-online.de [this message] 2022-11-28 18:15 ` [Bug tree-optimization/107898] " pinskia at gcc dot gnu.org 2022-11-29 8:03 ` [Bug c/107898] " rguenth at gcc dot gnu.org 2022-11-29 9:26 ` cvs-commit at gcc dot gnu.org 2022-11-29 9:27 ` [Bug c/107898] [11/12 " rguenth at gcc dot gnu.org 2022-11-29 14:29 ` amacleod at redhat dot com 2022-12-12 11:21 ` cvs-commit at gcc dot gnu.org 2023-05-05 13:34 ` [Bug c/107898] [11 " cvs-commit at gcc dot gnu.org 2023-05-05 13:34 ` rguenth 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-107898-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).