aboutsummaryrefslogtreecommitdiff
path: root/libcpp/include
diff options
context:
space:
mode:
authorJakub Jelinek <jakub@redhat.com>2021-12-01 10:16:57 +0100
committerJakub Jelinek <jakub@redhat.com>2021-12-01 10:16:57 +0100
commit35f2c098c81118020b1d288cd739108c8747a520 (patch)
treec056e49381ca148016b4c5d8f68f05c344d630f2 /libcpp/include
parentac5fd364f0978c62ae759e7b36ce6b912a27546c (diff)
downloadgcc-35f2c098c81118020b1d288cd739108c8747a520.zip
gcc-35f2c098c81118020b1d288cd739108c8747a520.tar.gz
gcc-35f2c098c81118020b1d288cd739108c8747a520.tar.bz2
simplify-rtx: Punt on simplify_associative_operation with large operands [PR102356]
Seems simplify_associate_operation is quadratic, which isn't a big deal for use during combine and other similar RTL passes, because those never try to combine expressions from more than a few instructions and because those instructions need to be recognized the machine description also bounds how many expressions can appear in there. var-tracking has depth limits only for some cases and unlimited depth for the vt_expand_loc though: /* This is the value used during expansion of locations. We want it to be unbounded, so that variables expanded deep in a recursion nest are fully evaluated, so that their values are cached correctly. We avoid recursion cycles through other means, and we don't unshare RTL, so excess complexity is not a problem. */ #define EXPR_DEPTH (INT_MAX) /* We use this to keep too-complex expressions from being emitted as location notes, and then to debug information. Users can trade compile time for ridiculously complex expressions, although they're seldom useful, and they may often have to be discarded as not representable anyway. */ #define EXPR_USE_DEPTH (param_max_vartrack_expr_depth) IMO for very large expressions it isn't worth trying to reassociate though, in fact e.g. for the new testcase below keeping it as is has bigger chance of generating smaller debug info which the dwarf2out.c part of the change tries to achieve - if a binary operation has the same operands, we can use DW_OP_dup and not bother computing the possibly large operand again. The patch fixes it by adding a counter to simplify_context and counting how many times simplify_associative_operation has been called during a single outermost simplify_* call, and once it reaches some maximum (currently 64), it stops reassociating. Another possibility to deal with the power expressions in debug info would be to introduce some new RTL operation for the pow{,i} (x, n) case, allow that solely in debug insns and expand those into DWARF using a loop. But that seems like quite a lot of work for something rarely used (especially when powi for larger n is only useful for 0 and 1 inputs because anything else overflows). 2021-12-01 Jakub Jelinek <jakub@redhat.com> PR rtl-optimization/102356 * rtl.h (simplify_context): Add assoc_count member and max_assoc_count static member. * simplify-rtx.c (simplify_associative_operation): Don't reassociate more than max_assoc_count times within one outermost simplify_* call. * dwarf2out.c (mem_loc_descriptor): Optimize binary operation with both operands the same using DW_OP_dup. * gcc.dg/pr102356.c: New test.
Diffstat (limited to 'libcpp/include')
0 files changed, 0 insertions, 0 deletions