From: "Jørgen Kvalsvik" <j@lambda.is>
To: gcc-patches@gcc.gnu.org
Cc: hjl.tools@gmail.com, rguenther@suse.de, hubicka@ucw.cz,
ro@CeBiTec.Uni-Bielefeld.DE, "Jørgen Kvalsvik" <j@lambda.is>
Subject: [PATCH 1/2] Remove unecessary and broken MC/DC compile test
Date: Fri, 5 Apr 2024 21:58:30 +0200 [thread overview]
Message-ID: <20240405195831.2728853-2-j@lambda.is> (raw)
In-Reply-To: <20240405195831.2728853-1-j@lambda.is>
The __sigsetjmp test was added as a regression test, which an early
iteration of the MC/DC support caused an internal compiler error,
triggered by a code path which did not make it through to the final
revision. Since this test really only worked on linux and does not
serve a purpose any more it can be removed.
gcc/testsuite/ChangeLog:
* gcc.misc-tests/gcov-19.c: Remove test.
---
gcc/testsuite/gcc.misc-tests/gcov-19.c | 11 -----------
1 file changed, 11 deletions(-)
diff --git a/gcc/testsuite/gcc.misc-tests/gcov-19.c b/gcc/testsuite/gcc.misc-tests/gcov-19.c
index 17f1fb4e923..b83a38531ba 100644
--- a/gcc/testsuite/gcc.misc-tests/gcov-19.c
+++ b/gcc/testsuite/gcc.misc-tests/gcov-19.c
@@ -869,17 +869,6 @@ dest:
goto * 0;
}
-int __sigsetjmp ();
-
-/* This should compile, but not called. */
-void
-mcdc021c ()
-{
- while (x) /* conditions(0/2) true(0) false(0)*/
- /* conditions(end) */
- __sigsetjmp ();
-}
-
/* If edges are not properly contracted the a && id (b) will be interpreted as
two independent expressions. */
void
--
2.30.2
next prev parent reply other threads:[~2024-04-05 19:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 19:58 [PATCH 0/2] Condition coverage fixes Jørgen Kvalsvik
2024-04-05 19:58 ` Jørgen Kvalsvik [this message]
2024-04-15 8:56 ` [PATCH 1/2] Remove unecessary and broken MC/DC compile test Rainer Orth
2024-04-05 19:58 ` [PATCH 2/2] Copy condition->expr map when inlining [PR114599] Jørgen Kvalsvik
2024-04-06 5:50 ` [PATCH 0/2] Condition coverage fixes Richard Biener
2024-04-06 11:15 ` Jørgen Kvalsvik
2024-04-06 20:41 ` Jørgen Kvalsvik
2024-04-07 6:26 ` Richard Biener
2024-04-07 7:28 ` Jørgen Kvalsvik
2024-04-08 6:31 ` Sam James
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=20240405195831.2728853-2-j@lambda.is \
--to=j@lambda.is \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=hubicka@ucw.cz \
--cc=rguenther@suse.de \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
/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).