public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/107311] New: New test case gcc.dg/c2x-enum-1.c fails Date: Wed, 19 Oct 2022 01:47:17 +0000 [thread overview] Message-ID: <bug-107311-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107311 Bug ID: 107311 Summary: New test case gcc.dg/c2x-enum-1.c fails Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: seurer at gcc dot gnu.org Target Milestone: --- g:3b3083a598ca3f4b6203284e01ed39ab6ff0844f, r13-3360-g3b3083a598ca3f make -k check-gcc RUNTESTFLAGS="--target_board=unix'{-m32}' dg.exp=gcc.dg/c2x-enum-1.c" FAIL: gcc.dg/c2x-enum-1.c (test for excess errors) This is failing with 32 bits on big endian powerpc64. 64 bits works fine. spawn -ignore SIGHUP /home/seurer/gcc/git/build/gcc-test/gcc/xgcc -B/home/seurer/gcc/git/build/gcc-test/gcc/ exceptions_enabled39558.cc -m32 -fdiagnostics-plain-output -S -o exceptions_enabled39558.s FAIL: gcc.dg/c2x-enum-1.c (test for excess errors) Excess errors: /home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/c2x-enum-1.c:8:47: error: pointer type mismatch in conditional expression Author: Joseph Myers <joseph@codesourcery.com> Date: Tue Oct 18 14:07:27 2022 +0000 c: C2x enums wider than int [PR36113]
next reply other threads:[~2022-10-19 1:47 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-19 1:47 seurer at gcc dot gnu.org [this message] 2022-10-19 7:24 ` [Bug c/107311] [13 regression] test case gcc.dg/c2x-enum-1.c fails after r13-3360-g3b3083a598ca3f rguenth at gcc dot gnu.org 2022-10-19 7:33 ` jakub at gcc dot gnu.org 2022-10-19 16:53 ` cvs-commit at gcc dot gnu.org 2022-10-19 17:12 ` jakub 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-107311-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).