public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/112887] during GIMPLE pass: phiopt ICE: Floating point exception (SIGFPE) at tree-ssa-phiopt.c:2224 with --param=l1-cache-line-size=0x20000000
Date: Sat, 09 Dec 2023 20:41:37 +0000	[thread overview]
Message-ID: <bug-112887-4-QGk9N4Pta7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112887-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:c250ff90989a71dff11e9256e99d2fa965ab1295

commit r14-6360-gc250ff90989a71dff11e9256e99d2fa965ab1295
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Sat Dec 9 21:41:00 2023 +0100

    phiopt: Fix ICE with large --param l1-cache-line-size= [PR112887]

    This function is never called when param_l1_cache_line_size is 0,
    but it uses int and unsigned int variables to hold alignment in
    bits, so for large param_l1_cache_line_size it is zero and e.g.
    DECL_ALIGN () % param_align_bits can divide by zero.
    Looking at the code, the function uses tree_fits_uhwi_p on the trees
    before converting them using tree_to_uhwi to int variables, which
    looks just wrong, either it would need to punt if it doesn't fit
    into those and also check for overflows during the computation,
    or use unsigned HOST_WIDE_INT for all of this.  That also fixes
    the division by zero, as param_l1_cache_line_size maximum is INT_MAX,
    that multiplied by 8 will always fit.

    2023-12-09  Jakub Jelinek  <jakub@redhat.com>

            PR tree-optimization/112887
            * tree-ssa-phiopt.cc (hoist_adjacent_loads): Change type of
            param_align, param_align_bits, offset1, offset2, size2 and align1
            variables from int or unsigned int to unsigned HOST_WIDE_INT.

            * gcc.dg/pr112887.c: New test.

  parent reply	other threads:[~2023-12-09 20:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-06 19:31 [Bug tree-optimization/112887] New: " zsojka at seznam dot cz
2023-12-06 19:53 ` [Bug tree-optimization/112887] " pinskia at gcc dot gnu.org
2023-12-07  8:16 ` rguenth at gcc dot gnu.org
2023-12-08 15:34 ` jakub at gcc dot gnu.org
2023-12-09 20:41 ` cvs-commit at gcc dot gnu.org [this message]
2023-12-09 20:42 ` 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-112887-4-QGk9N4Pta7@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).