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/79356] XPASS in attr-alloc_size-11.c Date: Tue, 28 Feb 2023 01:14:07 +0000 [thread overview] Message-ID: <bug-79356-4-vorfw7HP92@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-79356-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79356 --- Comment #16 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Hans-Peter Nilsson <hp@gcc.gnu.org>: https://gcc.gnu.org/g:2f2c0bc57be12ca92d3e2cc74f6cca048da9ed55 commit r13-6365-g2f2c0bc57be12ca92d3e2cc74f6cca048da9ed55 Author: Hans-Peter Nilsson <hp@axis.com> Date: Mon Feb 27 17:22:44 2023 +0100 testsuite: Add CRIS to targets not xfailing gcc.dg/attr-alloc_size-11.c:50,51 Reacting to a long-standing XPASS for CRIS. Maybe better do as https://gcc.gnu.org/PR79356#c11 suggests: xfail it for x86 only ...except I see m68k also does not xpass. testsuite: PR testsuite/79356 * gcc.dg/attr-alloc_size-11.c: Add CRIS to the list of targets excluding xfail on lines 50 and 51.
parent reply other threads:[~2023-02-28 1:14 UTC|newest] Thread overview: expand[flat|nested] mbox.gz Atom feed [parent not found: <bug-79356-4@http.gcc.gnu.org/bugzilla/>]
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-79356-4-vorfw7HP92@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).