From: Xi Ruoyao <xry111@xry111.site>
To: Aldy Hernandez <aldyh@redhat.com>, GCC patches <gcc-patches@gcc.gnu.org>
Cc: Chenghua Xu <xuchenghua@loongson.cn>, Lulu Cheng <chenglulu@loongson.cn>
Subject: Re: [PATCH 5/5] Convert ranger and clients to vrange.
Date: Mon, 27 Jun 2022 08:33:29 +0800 [thread overview]
Message-ID: <7000b5e7e1905fe2f6c328f97b61881ad73a3b8a.camel@xry111.site> (raw)
In-Reply-To: <CAGm3qMXkb8YnG1SU0Xwh_a5cBa2kB3Aa6nKck9OrsVtOhmYCKQ@mail.gmail.com>
On Wed, 2022-06-01 at 11:04 +0200, Aldy Hernandez via Gcc-patches wrote:
> Final patch committed.
>
> All users but one of Value_Range::set_type() have been removed in
> favor of using a constructor taking a type. We still need to delay
> initialization for one use in gimple_infer_range, as it has an array
> of temporaries for which the type is not known until later.
>
> Re-tested on x86-64 Linux.
Bootstrap on loongarch64-linux-gnu is broken since r13-911. I've
created https://gcc.gnu.org/PR106096 and put all information I've
gathered so far in the PR.
next prev parent reply other threads:[~2022-06-27 0:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-30 13:27 [PATCH 1/5] Implement abstract vrange class Aldy Hernandez
2022-05-30 13:27 ` [PATCH 2/5] Implement generic range temporaries Aldy Hernandez
2022-05-30 14:56 ` Andrew MacLeod
2022-05-31 6:21 ` Aldy Hernandez
2022-05-31 16:40 ` Andrew MacLeod
2022-06-01 9:01 ` Aldy Hernandez
2022-05-30 13:27 ` [PATCH 3/5] Convert range-op.* to vrange Aldy Hernandez
2022-06-01 9:01 ` Aldy Hernandez
2022-05-30 13:27 ` [PATCH 4/5] Revamp irange_allocator to handle vranges Aldy Hernandez
2022-06-01 9:02 ` Aldy Hernandez
2022-05-30 13:27 ` [PATCH 5/5] Convert ranger and clients to vrange Aldy Hernandez
2022-06-01 9:04 ` Aldy Hernandez
2022-06-27 0:33 ` Xi Ruoyao [this message]
2022-06-01 8:57 ` [PATCH 1/5] Implement abstract vrange class Aldy Hernandez
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=7000b5e7e1905fe2f6c328f97b61881ad73a3b8a.camel@xry111.site \
--to=xry111@xry111.site \
--cc=aldyh@redhat.com \
--cc=chenglulu@loongson.cn \
--cc=gcc-patches@gcc.gnu.org \
--cc=xuchenghua@loongson.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).