public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/109559] [12/13/14 Regression] Unexpected -Wmaybe-uninitialized warning when inlining with system header Date: Mon, 05 Feb 2024 12:36:25 +0000 [thread overview] Message-ID: <bug-109559-4-BEPaZvDSmW@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109559-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109559 --- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> --- So the 2nd hunk tests OK but the first for example runs into FAIL: gcc.dg/Wfree-nonheap-object-4.c (test for warnings, line 19) where we explicitly seem to expect the warning when the system header code is inlined into non-system-header context. That's btw the same that happens for the testcase in this bug - we inline the has_trivial_copy_and_destroy into integrate () which isn't in a system header. So it seems this was a deliberate choice ... which would mean the bug at hand is INVALID. (-Wno-system-headers has no effect)
next prev parent reply other threads:[~2024-02-05 12:36 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-19 20:23 [Bug middle-end/109559] New: " mpolacek at gcc dot gnu.org 2023-04-19 20:25 ` [Bug middle-end/109559] [12/13/14 Regression] " mpolacek at gcc dot gnu.org 2023-04-19 20:30 ` mpolacek at gcc dot gnu.org 2023-05-08 12:27 ` rguenth at gcc dot gnu.org 2024-01-12 10:29 ` rguenth at gcc dot gnu.org 2024-02-01 22:12 ` mpolacek at gcc dot gnu.org 2024-02-05 10:45 ` rguenth at gcc dot gnu.org 2024-02-05 12:36 ` rguenth at gcc dot gnu.org [this message] 2024-02-05 13:00 ` rguenth at gcc dot gnu.org 2024-02-06 9:53 ` rguenth at gcc dot gnu.org
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=bug-109559-4-BEPaZvDSmW@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).