public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug analyzer/111441] New: internal compiler error: in fold_binary_loc, at fold-const.cc:11580
@ 2023-09-17 8:44 dale.mengli.ming at proton dot me
2023-09-17 9:07 ` [Bug analyzer/111441] " pinskia at gcc dot gnu.org
` (8 more replies)
0 siblings, 9 replies; 10+ messages in thread
From: dale.mengli.ming at proton dot me @ 2023-09-17 8:44 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111441
Bug ID: 111441
Summary: internal compiler error: in fold_binary_loc, at
fold-const.cc:11580
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: analyzer
Assignee: dmalcolm at gcc dot gnu.org
Reporter: dale.mengli.ming at proton dot me
Target Milestone: ---
Thanks for taking the time to look into this case.
See it live: https://godbolt.org/z/Errh1v5rr.
When the line `__analyzer_describe(0, a[c]);` is commented out, the internal
compiler error disappears. Additionally, under the optimization levels `-O1` to
`-O3`, this error does not occur.
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Bug analyzer/111441] internal compiler error: in fold_binary_loc, at fold-const.cc:11580
2023-09-17 8:44 [Bug analyzer/111441] New: internal compiler error: in fold_binary_loc, at fold-const.cc:11580 dale.mengli.ming at proton dot me
@ 2023-09-17 9:07 ` pinskia at gcc dot gnu.org
2023-09-17 9:16 ` dale.mengli.ming at proton dot me
` (7 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: pinskia at gcc dot gnu.org @ 2023-09-17 9:07 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111441
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Created attachment 55916
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55916&action=edit
testcase
Please next time attach or place the testcase inline instead of just linking to
godbolt .
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Bug analyzer/111441] internal compiler error: in fold_binary_loc, at fold-const.cc:11580
2023-09-17 8:44 [Bug analyzer/111441] New: internal compiler error: in fold_binary_loc, at fold-const.cc:11580 dale.mengli.ming at proton dot me
2023-09-17 9:07 ` [Bug analyzer/111441] " pinskia at gcc dot gnu.org
@ 2023-09-17 9:16 ` dale.mengli.ming at proton dot me
2023-09-17 9:19 ` dale.mengli.ming at proton dot me
` (6 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: dale.mengli.ming at proton dot me @ 2023-09-17 9:16 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111441
--- Comment #2 from mengli ming <dale.mengli.ming at proton dot me> ---
(In reply to Andrew Pinski from comment #1)
> Created attachment 55916 [details]
> testcase
>
> Please next time attach or place the testcase inline instead of just linking
> to godbolt .
Thanks for the reminder, I'll make sure to do so next time.
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Bug analyzer/111441] internal compiler error: in fold_binary_loc, at fold-const.cc:11580
2023-09-17 8:44 [Bug analyzer/111441] New: internal compiler error: in fold_binary_loc, at fold-const.cc:11580 dale.mengli.ming at proton dot me
2023-09-17 9:07 ` [Bug analyzer/111441] " pinskia at gcc dot gnu.org
2023-09-17 9:16 ` dale.mengli.ming at proton dot me
@ 2023-09-17 9:19 ` dale.mengli.ming at proton dot me
2023-10-25 8:27 ` dale.mengli.ming at proton dot me
` (5 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: dale.mengli.ming at proton dot me @ 2023-09-17 9:19 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111441
--- Comment #3 from mengli ming <dale.mengli.ming at proton dot me> ---
Um..regarding the warning about "stack-based buffer over-read", it's a FP.
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Bug analyzer/111441] internal compiler error: in fold_binary_loc, at fold-const.cc:11580
2023-09-17 8:44 [Bug analyzer/111441] New: internal compiler error: in fold_binary_loc, at fold-const.cc:11580 dale.mengli.ming at proton dot me
` (2 preceding siblings ...)
2023-09-17 9:19 ` dale.mengli.ming at proton dot me
@ 2023-10-25 8:27 ` dale.mengli.ming at proton dot me
2024-02-14 14:40 ` [Bug analyzer/111441] [14 Regression] ICE generating access diagram, " dmalcolm at gcc dot gnu.org
` (4 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: dale.mengli.ming at proton dot me @ 2023-10-25 8:27 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111441
--- Comment #4 from mengli ming <dale.mengli.ming at proton dot me> ---
Hi, I've checked recently and the crash still persists, even with the -O0
optimization level.
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Bug analyzer/111441] [14 Regression] ICE generating access diagram, in fold_binary_loc, at fold-const.cc:11580
2023-09-17 8:44 [Bug analyzer/111441] New: internal compiler error: in fold_binary_loc, at fold-const.cc:11580 dale.mengli.ming at proton dot me
` (3 preceding siblings ...)
2023-10-25 8:27 ` dale.mengli.ming at proton dot me
@ 2024-02-14 14:40 ` dmalcolm at gcc dot gnu.org
2024-03-04 13:01 ` rguenth at gcc dot gnu.org
` (3 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: dmalcolm at gcc dot gnu.org @ 2024-02-14 14:40 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111441
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|internal compiler error: in |[14 Regression] ICE
|fold_binary_loc, at |generating access diagram,
|fold-const.cc:11580 |in fold_binary_loc, at
| |fold-const.cc:11580
Ever confirmed|0 |1
Last reconfirmed| |2024-02-14
Status|UNCONFIRMED |NEW
--- Comment #5 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Thanks for filing this. Still affects trunk, though I had to add a "void" to
the return type of f to avoid <source>:2:1: error: return type defaults to
'int' [-Wimplicit-int]:
https://godbolt.org/z/WM8zbvrxf
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Bug analyzer/111441] [14 Regression] ICE generating access diagram, in fold_binary_loc, at fold-const.cc:11580
2023-09-17 8:44 [Bug analyzer/111441] New: internal compiler error: in fold_binary_loc, at fold-const.cc:11580 dale.mengli.ming at proton dot me
` (4 preceding siblings ...)
2024-02-14 14:40 ` [Bug analyzer/111441] [14 Regression] ICE generating access diagram, " dmalcolm at gcc dot gnu.org
@ 2024-03-04 13:01 ` rguenth at gcc dot gnu.org
2024-03-07 22:29 ` law at gcc dot gnu.org
` (2 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: rguenth at gcc dot gnu.org @ 2024-03-04 13:01 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111441
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |14.0
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Bug analyzer/111441] [14 Regression] ICE generating access diagram, in fold_binary_loc, at fold-const.cc:11580
2023-09-17 8:44 [Bug analyzer/111441] New: internal compiler error: in fold_binary_loc, at fold-const.cc:11580 dale.mengli.ming at proton dot me
` (5 preceding siblings ...)
2024-03-04 13:01 ` rguenth at gcc dot gnu.org
@ 2024-03-07 22:29 ` law at gcc dot gnu.org
2024-03-18 22:47 ` cvs-commit at gcc dot gnu.org
2024-03-18 22:52 ` dmalcolm at gcc dot gnu.org
8 siblings, 0 replies; 10+ messages in thread
From: law at gcc dot gnu.org @ 2024-03-07 22:29 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111441
Jeffrey A. Law <law at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
CC| |law at gcc dot gnu.org
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Bug analyzer/111441] [14 Regression] ICE generating access diagram, in fold_binary_loc, at fold-const.cc:11580
2023-09-17 8:44 [Bug analyzer/111441] New: internal compiler error: in fold_binary_loc, at fold-const.cc:11580 dale.mengli.ming at proton dot me
` (6 preceding siblings ...)
2024-03-07 22:29 ` law at gcc dot gnu.org
@ 2024-03-18 22:47 ` cvs-commit at gcc dot gnu.org
2024-03-18 22:52 ` dmalcolm at gcc dot gnu.org
8 siblings, 0 replies; 10+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2024-03-18 22:47 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111441
--- Comment #6 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by David Malcolm <dmalcolm@gcc.gnu.org>:
https://gcc.gnu.org/g:1579394c9ecf3d1f678daa54b835c7fc3b76fb6d
commit r14-9527-g1579394c9ecf3d1f678daa54b835c7fc3b76fb6d
Author: David Malcolm <dmalcolm@redhat.com>
Date: Mon Mar 18 18:44:34 2024 -0400
analyzer: fix ICEs due to sloppy types in bounds-checking
[PR110902,PR110928,PR111305,PR111441]
Various analyzer ICEs in our bugzilla relate to sloppy use of types
within bounds-checking.
The bounds-checking code works by comparing symbolic *bit* offsets, and
we don't have a good user-facing type that can represent such an offset
(ptrdiff_type_node is for *byte* offsets).
ana::svalue doesn't enforce valid combinations of types for things like
binary operations. When I added the access diagrams for GCC 14, this
could lead to attempts to generate trees for such svalues, leading to
trees with invalid combinations of types (e.g. PLUS_EXPR or MULT_EXPR of
incompatible types), leading to ICEs inside the tree folding logic.
I tried two approaches to fixing this.
My first approach was to fix the type-handling throughout the
bounds-checking code to use correct types, using size_type_node for
sizes, ptrdiff_type_node for byte offsets, and trying ptrdiff_type_node
for bit offsets. I implemented this, and it fixed the crashes, but
unfortunately it led to:
(a) numerous false negatives from the bounds-checking code, due to it
becoming unable to be sure that the accessed offset was beyond the valid
bounds, due to the expressions involved gaining complicated sets of
nested casts.
(b) ugly access diagrams full of nested casts (for capacities, gap
measurements, etc)
So my second approach, implemented in this patch, is to accept that we
don't have a tree type for representing bit offsets. The patch
represents bit offsets using "typeless" symbolic values i.e. ones for
which get_type () is NULL_TREE, and implements enough support for basic
arithemetic as if these are mathematical integers (albeit ones for which
concrete values within an expression must fit within a signed wide int).
Such values can't be converted to tree, so the patch avoids such
conversions, instead implementing a new svalue::maybe_print_for_user for
printing them to a pretty_printer. The patch uses ptrdiff_type_node for
byte offsets.
Doing so fixes the crashes, whilst appearing to preserve the behavior of
-Wanalyzer-out-of-bounds in my testing.
gcc/analyzer/ChangeLog:
PR analyzer/110902
PR analyzer/110928
PR analyzer/111305
PR analyzer/111441
* access-diagram.cc: Include "analyzer/analyzer-selftests.h".
(get_access_size_str): Reimplement for conversion of
implmementation of bit_size_expr from tree to const svalue &. Use
svalue::maybe_print_for_user rather than tree printing routines.
(remove_ssa_names): Make non-static.
(bit_size_expr::get_formatted_str): Rename to...
(bit_size_expr::maybe_get_formatted_str): ...this, adding "model"
param and converting return type to a unique_ptr. Update for
conversion of implementation of bit_size_expr from tree to
const svalue &. Use svalue::maybe_print_for_user rather than tree
printing routines.
(bit_size_expr::print): Rename to...
(bit_size_expr::maybe_print_for_user): ...this, adding "model"
param and converting return type to bool. Update for
conversion of implementation of bit_size_expr from tree to
const svalue &. Use svalue::maybe_print_for_user rather than tree
printing routines.
(bit_size_expr::maybe_get_as_bytes): Add "mgr" param and convert
return type from tree to const svalue *; reimplement.
(access_range::access_range): Call strip_types when on
region_offset
intializations.
(access_range::get_size): Update for conversion of implementation
of bit_size_expr from tree to const svalue &.
(access_operation::get_valid_bits): Pass manager to access_range
ctor.
(access_operation::maybe_get_invalid_before_bits): Likewise.
(access_operation::maybe_get_invalid_after_bits): Likewise.
(boundaries::add): Likewise.
(bit_to_table_map::populate): Add "mgr" param and pass it to
access_range ctor.
(access_diagram_impl::access_diagram_impl): Pass manager to
bit_to_table_map::populate.
(access_diagram_impl::maybe_add_gap): Use svalue rather than tree
for symbolic bit offsets. Port to new bit_size_expr
representation.
(access_diagram_impl::add_valid_vs_invalid_ruler): Port to new
bit_size_expr representation.
(selftest::assert_eq_typeless_integer): New.
(ASSERT_EQ_TYPELESS_INTEGER): New.
(selftest::test_bit_size_expr_to_bytes): New.
(selftest::analyzer_access_diagram_cc_tests): New.
* access-diagram.h (class bit_size_expr): Reimplement, converting
implementation from tree to const svalue &.
(access_range::access_range): Add "mgr" param. Call strip_types
on region_offset initializations.
(access_range::get_size): Update decl for reimplementation.
* analyzer-selftests.cc (selftest::run_analyzer_selftests): Call
selftest::analyzer_access_diagram_cc_tests.
* analyzer-selftests.h
(selftest::analyzer_checker_script_cc_tests): Delete this stray
typo.
(selftest::analyzer_access_diagram_cc_tests): New decl.
* analyzer.h (print_expr_for_user): New decl.
(calc_symbolic_bit_offset): Update decl for reimplementation.
(strip_types): New decls.
(remove_ssa_names): New decl.
* bounds-checking.cc (strip_types): New.
(region_model::check_symbolic_bounds): Use typeless svalues.
* region-model-manager.cc
(region_model_manager::get_or_create_constant_svalue): Add "type"
param. Add overload with old signature.
(region_model_manager::get_or_create_int_cst): Support type being
NULL_TREE.
(region_model_manager::maybe_fold_unaryop): Gracefully reject
folding
of casts to NULL_TREE type.
(get_code_for_cast): Use NOP_EXPR for "casting" svalues to
NULL_TREE type.
(region_model_manager::get_or_create_cast): Support "casting"
svalues to NULL_TREE type.
(region_model_manager::maybe_fold_binop): Don't crash on inputs
with NULL_TREE type. Handle folding of binops on constants with
NULL_TREE type. Add missing cast from PR analyzer/110902.
Support enough folding of other ops on NULL_TREE type to support
bounds checking.
(region_model_manager::get_or_create_const_fn_result_svalue):
Remove assertion that type is nonnull.
* region-model-manager.h
(region_model_manager::get_or_create_constant_svalue): Add
overloaded decl taking a type.
(region_model_manager::maybe_fold_binop): Make public.
(region_model_manager::constants_map_t): Use
constant_svalue::key_t for the key, rather than just tree.
* region-model.cc (print_expr_for_user): New.
(selftest::test_array_2): Handle casts.
* region.cc (region_offset::calc_symbolic_bit_offset): Return
const svalue & rather than tree, and reimplement accordingly.
(region::calc_offset): Use ptrdiff_type_node for types of byte
offsets.
(region::maybe_print_for_user): New.
(element_region::get_relative_symbolic_offset): Use NULL_TREE for
types of bit offsets.
(offset_region::get_bit_offset): Likewise.
(sized_region::get_bit_size_sval): Likewise for bit sizes.
* region.h (region::maybe_print_for_user): New decl.
* svalue.cc (class auto_add_parens): New.
(svalue::maybe_print_for_user): New.
(svalue::cmp_ptr): Support typeless constant svalues.
(tristate_from_boolean_tree_node): New, taken from...
(constant_svalue::eval_condition): ...here. Handle comparison of
typeless integer svalue constants.
* svalue.h (svalue::maybe_print_for_user): New decl.
(class constant_svalue): Support the type of the svalue being
NULL_TREE.
(struct default_hash_traits<constant_svalue::key_t>): New.
gcc/ChangeLog:
PR analyzer/110902
PR analyzer/110928
PR analyzer/111305
PR analyzer/111441
* selftest.h (ASSERT_NE_AT): New macro.
gcc/testsuite/ChangeLog:
PR analyzer/110902
PR analyzer/110928
PR analyzer/111305
PR analyzer/111441
* c-c++-common/analyzer/out-of-bounds-const-fn.c: New test.
* c-c++-common/analyzer/out-of-bounds-diagram-11.c: Update
expected diagram output.
* c-c++-common/analyzer/out-of-bounds-diagram-pr110928.c: New test.
* c-c++-common/analyzer/out-of-bounds-diagram-pr111305.c: New test.
* c-c++-common/analyzer/out-of-bounds-diagram-pr111441.c: New test.
Signed-off-by: David Malcolm <dmalcolm@redhat.com>
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Bug analyzer/111441] [14 Regression] ICE generating access diagram, in fold_binary_loc, at fold-const.cc:11580
2023-09-17 8:44 [Bug analyzer/111441] New: internal compiler error: in fold_binary_loc, at fold-const.cc:11580 dale.mengli.ming at proton dot me
` (7 preceding siblings ...)
2024-03-18 22:47 ` cvs-commit at gcc dot gnu.org
@ 2024-03-18 22:52 ` dmalcolm at gcc dot gnu.org
8 siblings, 0 replies; 10+ messages in thread
From: dmalcolm at gcc dot gnu.org @ 2024-03-18 22:52 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111441
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Should be fixed by the above patch.
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2024-03-18 22:52 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-09-17 8:44 [Bug analyzer/111441] New: internal compiler error: in fold_binary_loc, at fold-const.cc:11580 dale.mengli.ming at proton dot me
2023-09-17 9:07 ` [Bug analyzer/111441] " pinskia at gcc dot gnu.org
2023-09-17 9:16 ` dale.mengli.ming at proton dot me
2023-09-17 9:19 ` dale.mengli.ming at proton dot me
2023-10-25 8:27 ` dale.mengli.ming at proton dot me
2024-02-14 14:40 ` [Bug analyzer/111441] [14 Regression] ICE generating access diagram, " dmalcolm at gcc dot gnu.org
2024-03-04 13:01 ` rguenth at gcc dot gnu.org
2024-03-07 22:29 ` law at gcc dot gnu.org
2024-03-18 22:47 ` cvs-commit at gcc dot gnu.org
2024-03-18 22:52 ` dmalcolm at gcc dot gnu.org
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).