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: Mon, 22 May 2023 14:50:47 +0000 [thread overview]
Message-ID: <bug-52641-4-Ed3JC3EbCf@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 #19 from CVS 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:9f5065094c9632a50bea604d5896a139609e50cf
commit r14-1074-g9f5065094c9632a50bea604d5896a139609e50cf
Author: Georg-Johann Lay <avr@gjlay.de>
Date: Mon May 22 16:47:56 2023 +0200
testsuite/52641: Fix tests that fail for 16-bit int / pointer targets.
gcc/testsuite/
PR testsuite/52641
* c-c++-common/pr19807-2.c: Use __SIZEOF_INT__ instead of 4.
* gcc.c-torture/compile/pr103813.c: Require size32plus.
* gcc.c-torture/execute/pr108498-2.c: Same.
* gcc.c-torture/compile/pr96426.c: Condition on
__SIZEOF_LONG_LONG__ == __SIZEOF_DOUBLE__.
* gcc.c-torture/execute/pr103417.c: Require int32plus.
* gcc.dg/pr104198.c: Same.
* gcc.dg/pr21137.c: Same.
* gcc.dg/pr88905.c: Same.
* gcc.dg/pr90838.c: Same.
* gcc.dg/pr97317.c: Same.
* gcc.dg/pr100292.c: Require int32.
* gcc.dg/pr101008.c: Same.
* gcc.dg/pr96542.c: Same.
* gcc.dg/pr96674.c: Same.
* gcc.dg/pr97750.c: Require ptr_eq_long.
next prev parent reply other threads:[~2023-05-22 14:50 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 [this message]
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
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-Ed3JC3EbCf@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: link
Be 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).