https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107985
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107985
--- Comment #6 from CVS Commits ---
The master branch has been updated by Andrew Macleod :
https://gcc.gnu.org/g:0ef9991d8767932f51fa97753c16058d17b29b18
commit r13-4557-g0ef9991d8767932f51fa97753c16058d17b29b18
Author: Andrew MacLeod
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107985
--- Comment #5 from Aldy Hernandez ---
(In reply to Andrew Macleod from comment #4)
> the gimple_range_op_handler constructor should check the operands for
> supported types as well before setting m_valid.
>
> There is also a ripple effect in g
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107985
--- Comment #4 from Andrew Macleod ---
the gimple_range_op_handler constructor should check the operands for supported
types as well before setting m_valid.
There is also a ripple effect in gimple_ranger::prefill_stmt_dependencies where
the ass
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107985
--- Comment #3 from Aldy Hernandez ---
Another alternative would be to add an is_a/as_a handler for unsupported_type's
in value-range.h and a corresponding entry for unsupported types in
range_operator:
virtual bool fold_range (irange &r, tree
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107985
Aldy Hernandez changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107985
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
--- Comment #1 from Andrew Pinski
