From: Jakub Jelinek <jakub@redhat.com>
To: "haochen.jiang" <haochenj@ecsmtp.sh.intel.com>
Cc: gcc-patches@gcc.gnu.org
Subject: [committed] testsuite: Fix up broken testcase [PR107127]
Date: Thu, 24 Nov 2022 10:37:09 +0100 [thread overview]
Message-ID: <Y387Ra+X63ssy1UG@tucnak> (raw)
In-Reply-To: <202211240137.2AO1bs8L789884@shliclel314.sh.intel.com>
Hi!
On Thu, Nov 24, 2022 at 09:37:54AM +0800, haochen.jiang wrote:
> 8a0fce6a51915c29584427fd376b40073c328090 is the first bad commit
> commit 8a0fce6a51915c29584427fd376b40073c328090
> Author: Jakub Jelinek <jakub@redhat.com>
> Date: Wed Nov 23 19:09:31 2022 +0100
>
> c: Fix compile time hog in c_genericize [PR107127]
>
> caused
>
> FAIL: gcc.dg/pr107127.c (test for excess errors)
Oops, sorry.
I've added { dg-options "" } line manually in the patch but
forgot to adjust the number of added lines.
Tested on x86_64-linux, committed to trunk as obvious.
2022-11-24 Jakub Jelinek <jakub@redhat.com>
PR c/107127
* gcc.dg/pr107127.c (foo): Add missing closing }.
--- gcc/testsuite/gcc.dg/pr107127.c.jj 2022-11-23 19:09:24.670333114 +0100
+++ gcc/testsuite/gcc.dg/pr107127.c 2022-11-24 10:31:48.208143681 +0100
@@ -10,3 +10,4 @@ foo (_Complex double a, double b, double
return v[0] / ((((c * (0 - 0 / a + 699.0 + 7.05 - 286.0 - +-4.65 + 1.57 + 0) * 0.1 - 3.28 + 4.22 + 0.1)) * b + 5.06)
* 1.23 * 8.0 * 12.0 * 16.0 * 2.0 * 2.0 * 0.25 * 0.125 * 18.2 * -15.25 * 0.0001
* 42.0 * 0.012 - 8.45 + 0 + 88.0 + 6.96 + 867.0 + 9.10 - 7.04 * -1.0);
+}
Jakub
prev parent reply other threads:[~2022-11-24 9:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 1:37 [r13-4268 Regression] FAIL: gcc.dg/pr107127.c (test for excess errors) on Linux/x86_64 haochen.jiang
2022-11-24 9:37 ` Jakub Jelinek [this message]
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=Y387Ra+X63ssy1UG@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=haochenj@ecsmtp.sh.intel.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).