public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <jeffreyalaw@gmail.com>
To: 钟居哲 <juzhe.zhong@rivai.ai>, patrick <patrick@rivosinc.com>,
	"pan2.li" <pan2.li@intel.com>, "rdapp.gcc" <rdapp.gcc@gmail.com>,
	gcc-patches <gcc-patches@gcc.gnu.org>
Cc: "kito.cheng" <kito.cheng@gmail.com>
Subject: Re: [PATCH v1] RISC-V: Revert RVV wv instructions overlap and xfail tests
Date: Thu, 25 Apr 2024 08:16:59 -0600	[thread overview]
Message-ID: <e638ebe5-3717-45a6-9a1c-41a35121eff8@gmail.com> (raw)
In-Reply-To: <4987EAADD3EAF406+2024042306075876990914@rivai.ai>



On 4/22/24 4:07 PM, 钟居哲 wrote:
> Apologize that we didn't post our (me, kito and Li Pan) disscussions.
> 
> This is the story:
> We found that my previous patches which support highpart register 
> overlap with register filter for instructions like (vwadd.wv)
> cause ICE reported by:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114714 <https:// 
> gcc.gnu.org/bugzilla/show_bug.cgi?id=114714>
> and this is obviously a regression (No ICE on GCC 13.2, but ICE on GCC 14)
Just a note for the future, this wouldn't really be considered a 
regression since GCC-13 didn't have any vector support.  I'm happy to 
help with this kind of judgment call, as are many other GCC developers 
such as Jakub, Richi, etc.  We've been making these kinds of judgment 
calls for decades.

> 
> We have tried several fixes to work around this ICE, however, we failed.
> And also I found my previous patches are quite wrong which is not the 
> perfect solution to support register group overlap
> for vwadd.wv.
> So, finally we decide to revert those patches.
It would have been useful to bring others into the discussion.  Both 
Robin and I would have likely wanted to understand why disabling the 
alternative wasn't sufficient.

Looking at this more generally, we need to keep in mind that the closer 
we get to a release, the more careful we need to be.  We can take the 
time to bring more engineers into the technical discussion.  We can take 
the time to evaluate the pros/cons of different approaches and balance 
them against the needs of the upcoming release and other factors that 
may come into play.

So let's learn, adjust & move on.

Thanks,
jeff



      parent reply	other threads:[~2024-04-25 14:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-19 14:29 pan2.li
2024-04-19 14:54 ` Robin Dapp
2024-04-19 23:24   ` Li, Pan2
2024-04-22 17:20     ` Patrick O'Neill
2024-04-22 22:07       ` 钟居哲
2024-04-23  0:42         ` Palmer Dabbelt
2024-04-23  1:44           ` Li, Pan2
2024-04-25 14:16         ` Jeff Law [this message]

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=e638ebe5-3717-45a6-9a1c-41a35121eff8@gmail.com \
    --to=jeffreyalaw@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=juzhe.zhong@rivai.ai \
    --cc=kito.cheng@gmail.com \
    --cc=pan2.li@intel.com \
    --cc=patrick@rivosinc.com \
    --cc=rdapp.gcc@gmail.com \
    /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).