This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [Patch ARM/testsuite 00/22] Neon intrinsics executable tests
- From: Christophe Lyon <christophe dot lyon at linaro dot org>
- To: Mike Stump <mikestump at comcast dot net>
- Cc: Ramana Radhakrishnan <ramrad01 at arm dot com>, gcc-patches <gcc-patches at gcc dot gnu dot org>
- Date: Thu, 12 Jun 2014 16:26:13 +0200
- Subject: Re: [Patch ARM/testsuite 00/22] Neon intrinsics executable tests
- Authentication-results: sourceware.org; auth=none
- References: <1402005882-31597-1-git-send-email-christophe dot lyon at linaro dot org> <CAJA7tRZUz3VT9vnJK6R4W9GRQ=12hDPojvnomo8=J3E8TgC=-A at mail dot gmail dot com> <C5BDB077-030B-4AFB-8C15-583BAEB267F4 at comcast dot net>
On 12 June 2014 04:31, Mike Stump <mikestump@comcast.net> wrote:
> On Jun 10, 2014, at 3:03 PM, Ramana Radhakrishnan <ramana.gcc@googlemail.com> wrote:
>> I am a bit ambivalent between getting folks to add scan-assembler
>> tests here and worrying between this and getting the behaviour
>> correct. Additionally if you add the complexity of scanning for
>> aarch64 as well this starts getting messy.
>>
>> At this point I'm going to wait to see if any of the testsuite
>> maintainers step in and comment and if not I'll start looking at this
>> properly early next week.
>
> [ ducks ] So, I wasnât going to commentâ If you guys do something really stupid, Iâll scream, as hopefully will others. Doing something a little misguided I donât think hurts much. The worst case if you figure out in a year or two why it was a bad idea and then fix it, not the end of the world.
If the execution part is OK and the scan-assembler is questionable, I
can just remove that part (or leave it commented until we decide
otherwise).