From: Paul Hua <paul.hua.gm@gmail.com>
To: Faraz Shahbazker <fshahbazker@wavecomp.com>
Cc: "binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: [PATCH 2/2] [MIPS] Add i6500 CPU and fix i6400 default ASEs
Date: Fri, 12 Apr 2019 01:14:00 -0000 [thread overview]
Message-ID: <CAKjxQHmfYTgsgr-7rRR+FGtD9k-v5490vUsHgvyMA0nqE8++uw@mail.gmail.com> (raw)
In-Reply-To: <DM5PR22MB068308E43E6D724E8503F783D02F0@DM5PR22MB0683.namprd22.prod.outlook.com>
Hi, Faraz,
> > FAIL: ELF i6500 markings
> Did you perhaps miss [PATCH 1/2] [MIPS] Apply ASE information for the selected processor?
I apply both patches, but refused, I changed by hand, maybe I miss
something, please let your patch base new repo and resend it.
>
> ASE information has been broken for processors which do not also correspond to unique `arch' designations. The testsuite does not include coverage for any such processor, so it was never detected. The first patch fixes this and the second adds new tests which rely upon it.
>
> Regards,
> Faraz
next prev parent reply other threads:[~2019-04-12 1:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 20:40 [PATCH 1/2] [MIPS] Apply ASE information for the selected processor Faraz Shahbazker
2019-04-09 20:40 ` [PATCH 2/2] [MIPS] Add i6500 CPU and fix i6400 default ASEs Faraz Shahbazker
2019-04-11 2:44 ` Paul Hua
2019-04-11 16:52 ` Faraz Shahbazker
2019-04-12 1:14 ` Paul Hua [this message]
2019-04-12 2:09 ` Faraz Shahbazker
2019-04-13 2:06 ` Paul Hua
2019-04-13 4:55 ` Faraz Shahbazker
2019-04-13 8:35 ` Paul Hua
2019-04-13 8:32 ` [PATCH 1/2] [MIPS] Apply ASE information for the selected processor Paul Hua
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=CAKjxQHmfYTgsgr-7rRR+FGtD9k-v5490vUsHgvyMA0nqE8++uw@mail.gmail.com \
--to=paul.hua.gm@gmail.com \
--cc=binutils@sourceware.org \
--cc=fshahbazker@wavecomp.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).