From: Richard Biener <rguenther@suse.de>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH] New uninit testcase
Date: Tue, 23 Aug 2022 12:30:56 +0000 (UTC) [thread overview]
Message-ID: <20220823123056.Gdi1TUAGRWJN9gW6u80pGr6_LbeHOlUso6sceUDp5vg@z> (raw)
I've reduced the following which doesn't seem covered in a good enough
way in the testsuite.
Pushed.
* gcc.dg/uninit-pred-10.c: New testcase.
---
gcc/testsuite/gcc.dg/uninit-pred-10.c | 36 +++++++++++++++++++++++++++
1 file changed, 36 insertions(+)
create mode 100644 gcc/testsuite/gcc.dg/uninit-pred-10.c
diff --git a/gcc/testsuite/gcc.dg/uninit-pred-10.c b/gcc/testsuite/gcc.dg/uninit-pred-10.c
new file mode 100644
index 00000000000..468b4d3ad4b
--- /dev/null
+++ b/gcc/testsuite/gcc.dg/uninit-pred-10.c
@@ -0,0 +1,36 @@
+/* { dg-do compile } */
+/* { dg-options "-O2 -Wuninitialized" } */
+
+enum demangle_component_type {
+ DEMANGLE_COMPONENT_NAME,
+ DEMANGLE_COMPONENT_REFERENCE
+};
+struct demangle_component {
+ enum demangle_component_type type;
+} d_print_comp_inner_mod_inner, *d_print_comp_inner_dc;
+struct d_print_mod {
+ struct d_print_mod *next;
+};
+struct d_print_info {
+ int templates;
+ struct d_print_mod *modifiers;
+};
+void d_print_comp_inner(struct d_print_info *dpi)
+{
+ int saved_templates, need_template_restore = 0;
+ switch (d_print_comp_inner_dc->type) {
+ case DEMANGLE_COMPONENT_NAME:
+ goto modifier;
+ case DEMANGLE_COMPONENT_REFERENCE:
+ saved_templates = dpi->templates;
+ need_template_restore = 1;
+ modifier:
+ struct d_print_mod dpm;
+ dpm.next = dpi->modifiers;
+ d_print_comp_inner_mod_inner = *d_print_comp_inner_dc;
+ d_print_comp_inner(dpi);
+ dpi->modifiers = dpm.next;
+ if (need_template_restore)
+ dpi->templates = saved_templates; /* { dg-bogus "uninitialized" } */
+ }
+}
--
2.35.3
next reply other threads:[~2022-08-23 12:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 12:30 Richard Biener [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-23 12:30 Richard Biener
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=20220823123056.Gdi1TUAGRWJN9gW6u80pGr6_LbeHOlUso6sceUDp5vg@z \
--to=rguenther@suse.de \
--cc=gcc-patches@gcc.gnu.org \
/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).