From: Jeff Law <jeffreyalaw@gmail.com>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: wangfeng@eswincomputing.com, GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH v3] RISC-V:Optimize the MASK opt generation
Date: Mon, 2 Oct 2023 12:06:52 -0600 [thread overview]
Message-ID: <e633c209-6327-4ff2-8d55-3dd533ca642f@gmail.com> (raw)
In-Reply-To: <CAGWvnynG5kTknOOR8c_spppm96tbG4FadEus20otF=bu1oyQ-A@mail.gmail.com>
On 10/2/23 12:03, David Edelsohn wrote:
> On Mon, Oct 2, 2023 at 1:59 PM Jeff Law <jeffreyalaw@gmail.com
> <mailto:jeffreyalaw@gmail.com>> wrote:
>
>
>
> On 10/2/23 11:20, David Edelsohn wrote:
> > Wang,
> >
> > The AWK portions of this patch broke bootstrap on AIX.
> >
> > Also, the AWK portions are common code, not RISC-V specific. I
> don't
> > see anywhere that the common portions of the patch were reviewed or
> > approved by anyone with authority to approve the changes to the
> AWK files.
> >
> > This patch should not have been committed without approval by a
> reviewer
> > with authority for that portion of the compiler and should have been
> > tested on targets other than RISC-V if common parts of the
> compiler were
> > changed.
> I acked the generic bits. So the lack of testing on another target is
> on me.
>
>
> Hi, Jeff
>
> Sorry. I didn't see a comment from a global reviewer in the V3 thread.
NP.
>
> I am using Gawk on AIX. After the change, I see a parse error from
> gawk. I'm rebuilding with a checkout just before the change to confirm
> that it was the source of the error, and it seems to be past that
> failure location. I didn't keep the exact error. Once I get past this
> build cycle, I'll reproduce it.
I think there's already a patch circulating which fixes this. It broke
at least one other platform. Hopefully it'll all be sorted out today.
jeff
next prev parent reply other threads:[~2023-10-02 18:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 17:20 David Edelsohn
2023-10-02 17:58 ` Jeff Law
2023-10-02 18:03 ` David Edelsohn
2023-10-02 18:06 ` Jeff Law [this message]
2023-10-03 2:38 ` Kito Cheng
2023-10-03 13:22 ` David Edelsohn
2023-10-03 16:55 ` Jeff Law
2023-10-07 1:00 ` Feng Wang
-- strict thread matches above, loose matches on Subject: below --
2023-09-06 2:02 Feng Wang
2023-09-06 3:42 ` Kito Cheng
2023-09-07 0:48 ` Tsukasa OI
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=e633c209-6327-4ff2-8d55-3dd533ca642f@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--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).