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/112729] gcc.target/i386/apx-interrupt-1.c etc. FAIL
Date: Wed, 29 Nov 2023 13:52:43 +0000 [thread overview]
Message-ID: <bug-112729-4-nGrTqxLEcQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112729-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112729
--- Comment #9 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Rainer Orth <ro@gcc.gnu.org>:
https://gcc.gnu.org/g:8ee480441eaec87ca6e0b0963fe9aade7edd1e8a
commit r14-5968-g8ee480441eaec87ca6e0b0963fe9aade7edd1e8a
Author: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Date: Wed Nov 29 14:52:04 2023 +0100
testsuite, i386: Only check for cfi directives if supported [PR112729]
gcc.target/i386/apx-interrupt-1.c and two more tests FAIL on Solaris/x86
with the native assembler. Like Darwin as, it doesn't support cfi
directives. Instead of adding more and more targets in every affected
test, this patch introduces a cfi effective-target keyword to check for
the prerequisite.
Tested on i386-pc-solaris2.11 (as and gas), x86_64-pc-linux-gnu, and
x86_64-apple-darwin23.1.0.
2023-11-24 Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
gcc/testsuite:
PR testsuite/112729
* lib/target-supports.exp (check_effective_target_cfi): New proc.
* gcc.target/i386/apx-interrupt-1.c: Require cfi instead of
skipping on *-*-darwin*.
* gcc.target/i386/apx-push2pop2_force_drap-1.c: Likewise.
* gcc.target/i386/apx-push2pop2-1.c: Likewise.
gcc:
PR testsuite/112729
* doc/sourcebuild.texi (Effective-Target Keywords, Environment
attributes): Document cfi.
next prev parent reply other threads:[~2023-11-29 13:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 15:10 [Bug testsuite/112729] New: " ro at gcc dot gnu.org
2023-11-27 15:10 ` [Bug testsuite/112729] " ro at gcc dot gnu.org
2023-11-27 15:14 ` ro at gcc dot gnu.org
2023-11-28 2:47 ` wwwhhhyyy333 at gmail dot com
2023-11-28 3:33 ` wwwhhhyyy333 at gmail dot com
2023-11-28 12:06 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-11-28 12:11 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-11-28 12:27 ` ro at gcc dot gnu.org
2023-11-28 13:34 ` wwwhhhyyy333 at gmail dot com
2023-11-29 0:52 ` cvs-commit at gcc dot gnu.org
2023-11-29 13:52 ` cvs-commit at gcc dot gnu.org [this message]
2023-11-29 13:57 ` ro 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-112729-4-nGrTqxLEcQ@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).