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 target/103686] ICE in rs6000_expand_new_builtin at rs6000-call.c:15946
Date: Thu, 03 Feb 2022 17:17:42 +0000	[thread overview]
Message-ID: <bug-103686-4-Ljr2mSuhYc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103686-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #12 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by William Schmidt <wschmidt@gcc.gnu.org>:

https://gcc.gnu.org/g:48bd780ee327c9ae6ffc0641e73cc1f4939fb204

commit r12-7030-g48bd780ee327c9ae6ffc0641e73cc1f4939fb204
Author: Bill Schmidt <wschmidt@linux.ibm.com>
Date:   Wed Feb 2 21:30:27 2022 -0600

    rs6000: Remove -m[no-]fold-gimple flag [PR103686]

    The -m[no-]fold-gimple flag was really intended primarily for internal
    testing while implementing GIMPLE folding for rs6000 vector built-in
    functions.  It ended up leaking into other places, causing problems such
    as PR103686 identifies.  Let's remove it.

    There are a number of tests in the testsuite that require adjustment.
    Some specify -mfold-gimple directly, which is the default, so that is
    handled by removing the option.  Others unnecessarily specify
    -mno-fold-gimple, as the tests work fine without this.  Again that is
    handled by removing the option.  There are a couple of extra variants of
    tests specifically for -mno-fold-gimple; for those, we can just remove the
    whole test.

    gcc.target/powerpc/builtins-1.c was more problematic.  It was written in
    such a way as to be extremely fragile.  For this one, I rewrote the whole
    test in a different style, using individual functions to test each
    built-in function.  These same tests are also largely covered by
    builtins-1-be-folded.c and builtins-1-le-folded.c, so I chose to
    explicitly make this test -mbig for simplicity, and use -O2 for clean code
    generation.  I made some slight modifications to the expected instruction
    counts as a result, and tested on both 32- and 64-bit.

    2022-02-02  Bill Schmidt  <wschmidt@linux.ibm.com>

    gcc/
            PR target/103686
            * config/rs6000/rs6000-builtin.cc (rs6000_gimple_fold_builtin):
Remove
            test for !rs6000_fold_gimple.
            * config/rs6000/rs6000.cc (rs6000_option_override_internal):
Likewise.
            * config/rs6000/rs6000.opt (mfold-gimple): Remove.

    gcc/testsuite/
            PR target/103686
            * gcc.target/powerpc/builtins-1-be-folded.c: Remove -mfold-gimple
            option.
            * gcc.target/powerpc/builtins-1-le-folded.c: Likewise.
            * gcc.target/powerpc/builtins-1.c: Rewrite to use small functions
and
            restrict to -O2 -mbig for predictability.  Adjust instruction
counts.
            * gcc.target/powerpc/builtins-5.c: Remove -mno-fold-gimple option.
            * gcc.target/powerpc/p8-vec-xl-xst.c: Likewise.
            * gcc.target/powerpc/pr83926.c: Likewise.
            * gcc.target/powerpc/pr86731-nogimplefold-longlong.c: Delete.
            * gcc.target/powerpc/pr86731-nogimplefold.c: Delete.
            * gcc.target/powerpc/swaps-p8-17.c: Remove -mno-fold-gimple option.

  parent reply	other threads:[~2022-02-03 17:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-13 13:54 [Bug target/103686] New: " marxin at gcc dot gnu.org
2021-12-13 13:54 ` [Bug target/103686] " marxin at gcc dot gnu.org
2021-12-13 14:54 ` wschmidt at gcc dot gnu.org
2021-12-14 15:49 ` bergner at gcc dot gnu.org
2021-12-14 16:02 ` bergner at gcc dot gnu.org
2021-12-14 16:52 ` wschmidt at gcc dot gnu.org
2021-12-14 16:53 ` wschmidt at gcc dot gnu.org
2021-12-14 17:00 ` wschmidt at gcc dot gnu.org
2022-01-04 10:00 ` rguenth at gcc dot gnu.org
2022-01-04 10:15 ` segher at gcc dot gnu.org
2022-01-04 15:18 ` bergner at gcc dot gnu.org
2022-01-19 22:19 ` wschmidt at gcc dot gnu.org
2022-01-20 16:19 ` willschm at gcc dot gnu.org
2022-02-03 17:17 ` cvs-commit at gcc dot gnu.org [this message]
2022-02-03 17:24 ` wschmidt 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-103686-4-Ljr2mSuhYc@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).