From: Lehua Ding <lehua.ding@rivai.ai>
To: gcc-patches@gcc.gnu.org
Cc: vmakarov@redhat.com, richard.sandiford@arm.com, juzhe.zhong@rivai.ai
Subject: Re: [PATCH 0/4] Add DF_LIVE_SUBREG data and apply to IRA and LRA
Date: Mon, 5 Feb 2024 15:01:23 +0800 [thread overview]
Message-ID: <06EF0816D222F2E3+13e7cace-9231-4a64-b257-aba2ac4f320e@rivai.ai> (raw)
In-Reply-To: <20240203105012.208998-1-lehua.ding@rivai.ai>
> For SPEC INT 2017, when using upstream GCC (whitout these patches), I get a
> coredump when training the peak case, so no data yet. The cause of the core
> dump still needs to be investigated.
Typo, SPEC INT 2017 -> SPEC FP 2017
Also There is a bad news, the score of specint 2017 (with these patches)
is dropped, a bit strange and I need to be locating the cause.
--
Best,
Lehua (RiVAI)
next prev parent reply other threads:[~2024-02-05 7:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-03 10:50 Lehua Ding
2024-02-03 10:50 ` [PATCH 1/4] df: Add -ftrack-subreg-liveness option Lehua Ding
2024-02-03 10:50 ` [PATCH 2/4] df: Add DF_LIVE_SUBREG problem Lehua Ding
2024-02-03 10:50 ` [PATCH 3/4] ira: Apply DF_LIVE_SUBREG data Lehua Ding
2024-05-01 16:21 ` Vladimir Makarov
2024-02-03 10:50 ` [PATCH 4/4] lra: " Lehua Ding
2024-05-01 16:24 ` Vladimir Makarov
2024-05-08 3:01 ` Lehua Ding
2024-05-08 16:29 ` Vladimir Makarov
2024-05-08 22:16 ` 钟居哲
2024-02-05 7:01 ` Lehua Ding [this message]
2024-02-05 16:10 ` [PATCH 0/4] Add DF_LIVE_SUBREG data and apply to IRA and LRA Jeff Law
2024-02-06 1:44 ` Lehua Ding
2024-02-06 13:43 ` Vladimir Makarov
2024-02-05 18:17 ` Joseph Myers
2024-02-06 1:44 ` Lehua Ding
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=06EF0816D222F2E3+13e7cace-9231-4a64-b257-aba2ac4f320e@rivai.ai \
--to=lehua.ding@rivai.ai \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
--cc=richard.sandiford@arm.com \
--cc=vmakarov@redhat.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).