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/112743] RISC-V: building FAIL with -march=rv64(or rv32)gc_zve32f_zvfh_zfh
Date: Sat, 02 Dec 2023 03:18:46 +0000	[thread overview]
Message-ID: <bug-112743-4-DM50hNidy8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112743-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Pan Li <panli@gcc.gnu.org>:

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

commit r14-6068-ge5bbeedcf7020dfa3870d11cf2b85bc048655698
Author: Pan Li <pan2.li@intel.com>
Date:   Thu Nov 30 15:08:50 2023 +0800

    RISC-V: Bugfix for legitimize move when get vec mode in zve32f

    If we want to extract 64bit value but ELEN < 64, we use RVV
    vector mode with EEW = 32 to extract the highpart and lowpart.
    However, this approach doesn't honor DFmode when movdf pattern
    when ZVE32f and of course results in ICE when zve32f.

    This patch would like to reuse the approach with some additional
    handing, consider lowpart bits is meaningless for FP mode, we need
    one int reg as bridge here. For example:

    rtx tmp = gen_rtx_reg (DImode)
    reg:DI = reg:DF (fmv.d.x) // Move DF reg to DI
    ...
    perform the extract for high and low parts
    ...
    reg:DF = reg:DI (fmv.x.d) // Move DI reg back to DF after all done

            PR target/112743

    gcc/ChangeLog:

            * config/riscv/riscv.cc (riscv_legitimize_move): Take the
            exist (U *mode) and handle DFmode like DImode when EEW is
            32bits for ZVE32F.

    gcc/testsuite/ChangeLog:

            * gcc.target/riscv/rvv/base/pr112743-2.c: New test.

    Signed-off-by: Pan Li <pan2.li@intel.com>

  parent reply	other threads:[~2023-12-02  3:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-28  8:16 [Bug c/112743] New: " juzhe.zhong at rivai dot ai
2023-11-28  8:19 ` [Bug c/112743] " pan2.li at intel dot com
2023-11-28 12:03 ` [Bug target/112743] " rguenth at gcc dot gnu.org
2023-11-29  6:51 ` cvs-commit at gcc dot gnu.org
2023-11-29  6:52 ` pan2.li at intel dot com
2023-12-02  3:18 ` cvs-commit at gcc dot gnu.org [this message]
2023-12-02 11:11 ` pan2.li at intel dot com
2023-12-02 13:59 ` juzhe.zhong at rivai dot ai

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-112743-4-DM50hNidy8@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).