public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "olegendo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/64659] [SH] Immedate values not used for atomic ops Date: Wed, 28 Jan 2015 21:12:00 -0000 [thread overview] Message-ID: <bug-64659-4-DdM7xKweJH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64659-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64659 --- Comment #3 from Oleg Endo <olegendo at gcc dot gnu.org> --- Author: olegendo Date: Wed Jan 28 21:11:37 2015 New Revision: 220217 URL: https://gcc.gnu.org/viewcvs?rev=220217&root=gcc&view=rev Log: gcc/ PR target/64659 * config/sh/predicates.md (atomic_arith_operand, atomic_logical_operand): Remove. * config/sh/sync.md (fetchop_predicate, fetchop_constraint): Remove. (atomic_arith_operand_0): New predicate. (atomic_compare_and_swap<mode>): Use arith_reg_dest for output values. Use atomic_arith_operand_0 for input values. (atomic_compare_and_swapsi_hard, atomic_compare_and_swap<mode>_hard, atomic_compare_and_swap<mode>_soft_gusa, atomic_compare_and_swap<mode>_soft_tcb, atomic_compare_and_swap<mode>_soft_imask): Use arith_reg_dest and arith_reg_operand instead of register_operand. (atomic_exchange<mode>): Use arith_reg_dest for output value. Use atomic_arith_operand_0 for newval input. (atomic_exchangesi_hard, atomic_exchange<mode>_hard, atomic_exchange<mode>_soft_gusa, atomic_exchange<mode>_soft_tcb, atomic_exchange<mode>_soft_imask): Use arith_reg_dest and arith_reg_operand instead of register_operand. (atomic_arith_operand_1, atomic_logical_operand_1): New predicates. fetchop_predicate_1, fetchop_constraint_1_llcs, fetchop_constraint_1_gusa, fetchop_constraint_1_tcb, fetchop_constraint_1_imask): New code iterator attributes. (atomic_fetch_<fetchop_name><mode>): Use arith_reg_dest instead of register_operand. Use fetchop_predicate_1. (atomic_fetch_<fetchop_name>si_hard, atomic_fetch_<fetchop_name><mode>_hard): Use arith_reg_dest instead of register_operand. Use fetchop_predicate_1, fetchop_constraint_1_llcs. (atomic_fetch_<fetchop_name><mode>_soft_gusa): Use arith_reg_dest and arith_reg_operand instead of register_operand. Use fetchop_predicate_1, fetchop_constraint_1_gusa. (atomic_fetch_<fetchop_name><mode>_soft_tcb): Use arith_reg_dest and arith_reg_operand instead of register_operand. Use fetchop_predicate_1, fetchop_constraint_1_tcb. Adjust asm sequence to allow R0 usage. (atomic_fetch_<fetchop_name><mode>_soft_imask): Use arith_reg_dest and arith_reg_operand instead of register_operand. Use fetchop_predicate_1, fetchop_constraint_1_imask. Adjust asm sequence to allow R0 usage. (atomic_fetch_nand<mode>): Use arith_reg_dest instead of register_operand. Use atomic_logical_operand_1. (atomic_fetch_nandsi_hard, atomic_fetch_nand<mode>_hard, atomic_fetch_nand<mode>_soft_gusa): Use arith_reg_dest and arith_reg_operand instead of register_operand. (atomic_fetch_nand<mode>_soft_tcb, atomic_fetch_nand<mode>_soft_imask): Use arith_reg_dest and arith_reg_operand instead of register_operand. Use logical_operand and rK08. Adjust asm sequence to allow R0 usage. (atomic_<fetchop_name>_fetch<mode>): Use arith_reg_dest instead of register_operand. Use fetchop_predicate_1. (atomic_<fetchop_name>_fetchsi_hard, atomic_<fetchop_name>_fetch<mode>_hard): Use arith_reg_dest and arith_reg_operand instead of register_operand. Use fetchop_predicate_1, fetchop_constraint_1_llcs. (atomic_<fetchop_name>_fetch<mode>_soft_gusa): Use arith_reg_dest and arith_reg_operand instead of register_operand. Use fetchop_predicate_1, fetchop_constraint_1_gusa. (atomic_<fetchop_name>_fetch<mode>_soft_tcb): Use arith_reg_dest and arith_reg_operand instead of register_operand. Use fetchop_predicate_1, fetchop_constraint_1_tcb. Adjust asm sequence to allow R0 usage. (atomic_<fetchop_name>_fetch<mode>_soft_imask): Use arith_reg_dest and arith_reg_operand instead of register_operand. Use fetchop_predicate_1, fetchop_constraint_1_imask. Adjust asm sequence to allow R0 usage. (atomic_nand_fetch<mode>): Use arith_reg_dest instead of register_operand. Use atomic_logical_operand_1. (atomic_nand_fetchsi_hard, atomic_nand_fetch<mode>_hard, atomic_nand_fetch<mode>_soft_gusa): Use arith_reg_dest and arith_reg_operand instead of register_operand. (atomic_nand_fetch<mode>_soft_tcb): Use arith_reg_dest and arith_reg_operand instead of register_operand. Use logical_operand and K08. Adjust asm sequence to allow R0 usage. (atomic_nand_fetch<mode>_soft_imask): Use arith_reg_dest and arith_reg_operand instead of register_operand. Use logical_operand and K08. gcc/testsuite/ PR target/64659 * gcc.target/sh/sh.exp (check_effective_target_atomic_model_soft_gusa_available, check_effective_target_atomic_model_soft_tcb_available, check_effective_target_atomic_model_soft_imask_available, check_effective_target_atomic_model_hard_llcs_available): New. * gcc.target/sh/pr64659-0.h: New. * gcc.target/sh/pr64659-1.c: New. * gcc.target/sh/pr64659-2.c: New. * gcc.target/sh/pr64659-3.c: New. * gcc.target/sh/pr64659-4.c: New. Added: trunk/gcc/testsuite/gcc.target/sh/pr64659-0.h trunk/gcc/testsuite/gcc.target/sh/pr64659-1.c trunk/gcc/testsuite/gcc.target/sh/pr64659-2.c trunk/gcc/testsuite/gcc.target/sh/pr64659-3.c trunk/gcc/testsuite/gcc.target/sh/pr64659-4.c Modified: trunk/gcc/ChangeLog trunk/gcc/config/sh/predicates.md trunk/gcc/config/sh/sync.md trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/gcc.target/sh/sh.exp
next prev parent reply other threads:[~2015-01-28 21:12 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-01-18 21:37 [Bug target/64659] New: " olegendo at gcc dot gnu.org 2015-01-18 22:22 ` [Bug target/64659] " olegendo at gcc dot gnu.org 2015-01-18 22:40 ` olegendo at gcc dot gnu.org 2015-01-28 21:12 ` olegendo at gcc dot gnu.org [this message] 2015-02-01 10:47 ` olegendo 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-64659-4-DdM7xKweJH@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).