public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/112419] New: [14 Regression] gcc.dg/Wnonnull-4.c excess error for 32-bit targets Date: Tue, 07 Nov 2023 03:44:58 +0000 [thread overview] Message-ID: <bug-112419-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112419 Bug ID: 112419 Summary: [14 Regression] gcc.dg/Wnonnull-4.c excess error for 32-bit targets Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: diagnostic Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: hp at gcc dot gnu.org CC: uecker at gcc dot gnu.org Target Milestone: --- This test started failing with r14-5115-g6e9ee44d96e5 thus: Running /x/gcc/testsuite/gcc.dg/dg.exp ... FAIL: gcc.dg/Wnonnull-4.c (test for excess errors) In gcc.log (after all PASS lines): FAIL: gcc.dg/Wnonnull-4.c (test for excess errors) Excess errors: /o/gcc/gcc/testsuite/gcc.dg/Wnonnull-4.c:144:3: warning: 'fda_n_5' specified size 4294967256 exceeds maximum object size 2147483647 [-Wstringop-overflow=] The same happen for all 32-bit targets (including 64-bit targets when testing with a "-m32"-type option), according to posts to gcc-testresults@ around this commit.
next reply other threads:[~2023-11-07 3:44 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-07 3:44 hp at gcc dot gnu.org [this message] 2023-11-07 6:05 ` [Bug tree-optimization/112419] " uecker at gcc dot gnu.org 2023-11-07 8:44 ` [Bug testsuite/112419] " rguenth at gcc dot gnu.org 2023-11-07 15:33 ` hp at gcc dot gnu.org 2023-11-16 4:28 ` hp at gcc dot gnu.org 2023-11-16 5:23 ` uecker at gcc dot gnu.org 2023-12-06 0:47 ` cvs-commit at gcc dot gnu.org 2024-01-15 13:58 ` rguenth at gcc dot gnu.org 2024-01-16 2:19 ` hp 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-112419-4@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).