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/52641] Test cases fail for 16-bit int targets Date: Sun, 07 Jan 2024 12:44:58 +0000 [thread overview] Message-ID: <bug-52641-4-c22YDXOtQH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52641-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52641 --- Comment #23 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Georg-Johann Lay <gjl@gcc.gnu.org>: https://gcc.gnu.org/g:7d60b1b78538c5606e8d35cdba8f565e7785d9c6 commit r14-6981-g7d60b1b78538c5606e8d35cdba8f565e7785d9c6 Author: Georg-Johann Lay <avr@gjlay.de> Date: Sun Jan 7 13:17:19 2024 +0100 testsuite/52641: Fix fallout from sloppy tests. gcc/testsuite/ PR testsuite/52641 * gcc.dg/memchr-3.c [avr]: Anticipate -Wbuiltin-declaration-mismatch. * gcc.dg/pr103207.c: Use __INT32_TYPE__ instead of int. * gcc.dg/pr103451.c [void* != long]: Anticipate -Wpointer-to-int-cast. * gcc.dg/pr110496.c [void* != long]: Anticipate -Wint-to-pointer-cast. * gcc.dg/pr109977.c: Use __SIZEOF_DOUBLE__ instead of 8. * gcc.dg/pr110506-2.c: Use __UINT32_TYPE__ for uint32_t. * gcc.dg/pr110582.c: Require int32plus. * gcc.dg/pr111039.c: [sizeof(int) < 4]: Use __INT32_TYPE__. * gcc.dg/pr111599.c: Same. * gcc.dg/builtin-dynamic-object-size-0.c: Require size20plus. * gcc.dg/builtin-object-size-1.c [avr]: Skip tests with strndup. * gcc.dg/builtin-object-size-2.c: Same. * gcc.dg/builtin-object-size-3.c: Same. * gcc.dg/builtin-object-size-4.c: Same. * gcc.dg/pr111070.c: Use __UINTPTR_TYPE__ instead of unsigned long. * gcc.dg/debug/btf/btf-pr106773.c: Same. * gcc.dg/debug/btf/btf-bitfields-2.c: [sizeof(int) < 4]: Use __UINT32_TYPE__.
next prev parent reply other threads:[~2024-01-07 12:44 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-03-20 19:36 [Bug testsuite/52641] New: " gjl at gcc dot gnu.org 2012-03-20 19:39 ` [Bug testsuite/52641] " gjl at gcc dot gnu.org 2012-03-20 20:32 ` gjl at gcc dot gnu.org 2012-03-21 10:51 ` gjl at gcc dot gnu.org 2012-03-21 17:47 ` hp at gcc dot gnu.org 2012-04-24 17:08 ` gjl at gcc dot gnu.org 2012-04-24 17:20 ` gjl at gcc dot gnu.org 2012-05-16 12:48 ` gjl at gcc dot gnu.org 2012-11-23 10:09 ` gjl at gcc dot gnu.org 2012-11-26 18:47 ` gjl at gcc dot gnu.org 2013-03-04 11:13 ` gjl at gcc dot gnu.org 2013-08-14 15:37 ` amylaar at gcc dot gnu.org 2013-08-29 13:15 ` jakub at gcc dot gnu.org 2023-05-22 14:50 ` cvs-commit at gcc dot gnu.org 2023-05-22 18:21 ` cvs-commit at gcc dot gnu.org 2023-05-30 20:05 ` cvs-commit at gcc dot gnu.org 2024-01-07 12:44 ` cvs-commit at gcc dot gnu.org 2024-01-07 12:44 ` cvs-commit at gcc dot gnu.org [this message] 2024-01-07 15:54 ` cvs-commit at gcc dot gnu.org 2024-07-01 11:07 ` cvs-commit 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-52641-4-c22YDXOtQH@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).