On 12/7/20 9:19 AM, Martin Sebor wrote:
> On 12/4/20 3:17 PM, Jeff Law via Gcc-patches wrote:
>>
>>
>> On 12/4/20 2:55 PM, Mike Stump wrote:
>>> On Nov 30, 2020, at 8:00 AM, Jeff Law via Gcc-patches
>>> wrote:
This patch fixes a handful of tests with non-unique names which
confuse
>>>
On 12/4/20 3:17 PM, Jeff Law via Gcc-patches wrote:
On 12/4/20 2:55 PM, Mike Stump wrote:
On Nov 30, 2020, at 8:00 AM, Jeff Law via Gcc-patches
wrote:
This patch fixes a handful of tests with non-unique names which confuse
the living hell out of compare_tests, particularly if one of two tes
On 12/4/20 2:55 PM, Mike Stump wrote:
> On Nov 30, 2020, at 8:00 AM, Jeff Law via Gcc-patches
> wrote:
>> This patch fixes a handful of tests with non-unique names which confuse
>> the living hell out of compare_tests, particularly if one of two tests
>> [x]fail while the other is [x]pass whic
On Nov 30, 2020, at 8:00 AM, Jeff Law via Gcc-patches
wrote:
>
> This patch fixes a handful of tests with non-unique names which confuse
> the living hell out of compare_tests, particularly if one of two tests
> [x]fail while the other is [x]pass which compare_tests will flag as a
> regression e
This patch fixes a handful of tests with non-unique names which confuse
the living hell out of compare_tests, particularly if one of two tests
[x]fail while the other is [x]pass which compare_tests will flag as a
regression each and every run.
No doubt there's a lot more of these lying around and
