public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/113428] [14 regression] gcc.dg/gomp/bad-array-section-c-3.c fails after r14-7158-gb5476e4c881b0d Date: Mon, 11 Mar 2024 15:52:22 +0000 [thread overview] Message-ID: <bug-113428-4-nNvjWignC5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113428-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113428 --- Comment #7 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Richard Earnshaw <rearnsha@gcc.gnu.org>: https://gcc.gnu.org/g:c27b30552e6cc789425d3628d294dafc5f3a0861 commit r14-9430-gc27b30552e6cc789425d3628d294dafc5f3a0861 Author: Richard Earnshaw <rearnsha@arm.com> Date: Wed Mar 6 13:41:02 2024 +0000 gomp: testsuite: improve compatibility of bad-array-section-3.c [PR113428] This test generates different warnings on ilp32 targets because the size of an integer matches the size of a pointer. Avoid this by using signed char. gcc/testsuite: PR testsuite/113428 * gcc.dg/gomp/bad-array-section-c-3.c: Use signed char instead of int.
next prev parent reply other threads:[~2024-03-11 15:52 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-16 19:18 [Bug testsuite/113428] New: " seurer at gcc dot gnu.org 2024-01-17 8:00 ` [Bug testsuite/113428] " rguenth at gcc dot gnu.org 2024-01-17 9:22 ` clyon at gcc dot gnu.org 2024-01-17 13:46 ` ro at gcc dot gnu.org 2024-03-06 10:00 ` rearnsha at gcc dot gnu.org 2024-03-06 10:06 ` rearnsha at gcc dot gnu.org 2024-03-06 15:24 ` dave.anglin at bell dot net 2024-03-06 17:24 ` rearnsha at gcc dot gnu.org 2024-03-07 20:51 ` law at gcc dot gnu.org 2024-03-11 15:52 ` cvs-commit at gcc dot gnu.org [this message] 2024-03-11 17:19 ` rearnsha 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-113428-4-nNvjWignC5@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).