From: "Li, Pan2" <pan2.li@intel.com>
To: Andreas Schwab <schwab@linux-m68k.org>,
"juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>
Cc: yulong <shiyulong@iscas.ac.cn>,
gcc-patches <gcc-patches@gcc.gnu.org>,
palmer <palmer@dabbelt.com>, Kito.cheng <kito.cheng@sifive.com>,
Jim Wilson <jim.wilson.gcc@gmail.com>,
wuwei2016 <wuwei2016@iscas.ac.cn>, jiawei <jiawei@iscas.ac.cn>,
shihua <shihua@iscas.ac.cn>, dje.gcc <dje.gcc@gmail.com>,
mirimmad <mirimmad@outlook.com>, jakub <jakub@redhat.com>,
jeffreyalaw <jeffreyalaw@gmail.com>
Subject: RE: [PATCH V1] RISC-V:Add float16 tuple type support
Date: Sun, 25 Jun 2023 07:31:36 +0000 [thread overview]
Message-ID: <MW5PR11MB59081E59FBBB93EE06A0656DA921A@MW5PR11MB5908.namprd11.prod.outlook.com> (raw)
In-Reply-To: <87wmzs80sg.fsf@linux-m68k.org>
Sure, reverted and will commit this patch after the issue addressed.
Pan
-----Original Message-----
From: Andreas Schwab <schwab@linux-m68k.org>
Sent: Sunday, June 25, 2023 3:22 PM
To: juzhe.zhong@rivai.ai
Cc: yulong <shiyulong@iscas.ac.cn>; gcc-patches <gcc-patches@gcc.gnu.org>; palmer <palmer@dabbelt.com>; Kito.cheng <kito.cheng@sifive.com>; Jim Wilson <jim.wilson.gcc@gmail.com>; Li, Pan2 <pan2.li@intel.com>; wuwei2016 <wuwei2016@iscas.ac.cn>; jiawei <jiawei@iscas.ac.cn>; shihua <shihua@iscas.ac.cn>; dje.gcc <dje.gcc@gmail.com>; mirimmad <mirimmad@outlook.com>; jakub <jakub@redhat.com>; jeffreyalaw <jeffreyalaw@gmail.com>
Subject: Re: [PATCH V1] RISC-V:Add float16 tuple type support
Please revert until bootstrap is restored.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
prev parent reply other threads:[~2023-06-25 7:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 5:40 shiyulong
2023-06-15 6:09 ` juzhe.zhong
2023-06-17 22:07 ` Jeff Law
2023-06-18 2:12 ` Li, Pan2
2023-06-23 10:25 ` Andreas Schwab
2023-06-25 2:16 ` juzhe.zhong
2023-06-25 7:21 ` Andreas Schwab
2023-06-25 7:31 ` Li, Pan2 [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=MW5PR11MB59081E59FBBB93EE06A0656DA921A@MW5PR11MB5908.namprd11.prod.outlook.com \
--to=pan2.li@intel.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=jeffreyalaw@gmail.com \
--cc=jiawei@iscas.ac.cn \
--cc=jim.wilson.gcc@gmail.com \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@sifive.com \
--cc=mirimmad@outlook.com \
--cc=palmer@dabbelt.com \
--cc=schwab@linux-m68k.org \
--cc=shihua@iscas.ac.cn \
--cc=shiyulong@iscas.ac.cn \
--cc=wuwei2016@iscas.ac.cn \
/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).