From: Gerald Pfeifer <gerald@pfeifer.com>
To: Kito Cheng <kito.cheng@gmail.com>
Cc: Jeff Law <jeffreyalaw@gmail.com>,
Feng Wang <wangfeng@eswincomputing.com>,
gcc-patches@gcc.gnu.org
Subject: Re: [PATCH v6] RISC-V:Optimize the MASK opt generation
Date: Mon, 2 Oct 2023 13:09:31 +0200 (CEST) [thread overview]
Message-ID: <69789f64-f045-241a-9fa8-7199265634a3@pfeifer.com> (raw)
In-Reply-To: <CA+yXCZBJTysy0omAETJ3PP59c6dqy5RAKEeVQ1f6f-g8EKqtPg@mail.gmail.com>
On Mon, 2 Oct 2023, Kito Cheng wrote:
> Thanks for reporting this issue, I just realized multidimensional
> arrays are gawk extensions, could you try the attached patch to see if
> it can resolve the issue?
Yes, with that patch applied the build proceeds far beyond that point
(still running).
Thanks for the quick fix!
Gerald
prev parent reply other threads:[~2023-10-02 11:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 9:18 Feng Wang
2023-09-29 18:05 ` Kito Cheng
2023-09-29 18:09 ` Jeff Law
2023-09-29 19:33 ` Jeff Law
2023-10-01 8:10 ` Kito Cheng
2023-10-01 20:56 ` Gerald Pfeifer
2023-10-02 2:55 ` Kito Cheng
2023-10-02 5:42 ` Jan-Benedict Glaw
2023-10-02 11:09 ` Gerald Pfeifer [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=69789f64-f045-241a-9fa8-7199265634a3@pfeifer.com \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=kito.cheng@gmail.com \
--cc=wangfeng@eswincomputing.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).