This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH v2] PR92090: Fix testcase failures by r276469
- From: Joseph Myers <joseph at codesourcery dot com>
- To: Kewen.Lin <linkw at linux dot ibm dot com>
- Cc: luoxhu <luoxhu at linux dot ibm dot com>, Segher Boessenkool <segher at kernel dot crashing dot org>, <gcc-patches at gcc dot gnu dot org>, <hubicka at ucw dot cz>, <wschmidt at linux dot ibm dot com>
- Date: Tue, 5 Nov 2019 18:20:25 +0000
- Subject: Re: [PATCH v2] PR92090: Fix testcase failures by r276469
- Ironport-sdr: TJE61FSH+w7ybGz0SwikCM9r5dvvGKxvsKWPgxGxyi8QBQHWnaZpTeXUAuOXpJYnDbq5+tD0xX 72YKB0xFMTZ52F/VUQrDJp7MfCjdAwgCd3TjVM4hSV+KckVWYgCGCDhOmkPN+2rV2yFvkqvHdR hTCHKgtGXaB6Xv7K3nvXEHe808HR1o/KN/rVBnHSDx/sRe3tVbdX08xTazjbqG1ZJJ6JzjudSf YY0K4HbMVSAW7V34vur9XjMwrySb3EFsQLj1lFdmNMDcehdCOCum/8+qmleU9GLCpVZ0B+7R/l e6k=
- Ironport-sdr: DIG+Clna37oxpn5WsnzPrCLiAIjrBNAJFhaJFhD52v4mOHIlnPtWH2jlXdPyrQuas0ShrsDfU9 aIRFj6wOkxYxmmFMWLdLEUjfrrnhrAfWyL2HyDXQlJLztz3nUhmUENlBOTjE8GCwTtMxG2b070 CZzHi5gCg+d2TgIlyh5DdWUJLA8wEUcOAH3Mw7S4eCCeYHZ0Esn3QuBy5iyT/c3LGr3d9tFTLr GGZccYSidnPPsf/SZP7wLACoagw6M6pDgBNqohG45rFDQ1IN1STbqcV+pCckuY7tBxscVCeB6j 4hg=
- References: <20191030070244.127375-1-luoxhu@linux.ibm.com> <20191030222749.GQ28442@gate.crashing.org> <ad3c665d-1850-3bbd-2a35-d04ee88dc0cc@linux.ibm.com> <alpine.DEB.2.21.1911042252150.28544@digraph.polyomino.org.uk> <84d74542-1e88-8c5d-920f-2423b7d4392e@linux.ibm.com>
On Tue, 5 Nov 2019, Kewen.Lin wrote:
> Very good point! Since gcc doesn't pursue 100% testsuite pass rate, I noticed
> there are a few failures exposed/caused by some PRs all the time. Could we
> just leave the test case there without any pre workaround till the PR get fixed?
Yes, leaving the test as-is would be typical in GCC (though there is also
an argument for XFAILing and filing bugs to try to keep the baseline
testsuite state clean and instead use only Bugzilla to track known
regressions).
--
Joseph S. Myers
joseph@codesourcery.com