public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "chrbr at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/52144] ARM should support arm/thumb function attribute to permit different instruction sets in the same source Date: Mon, 22 Jun 2015 07:32:00 -0000 [thread overview] Message-ID: <bug-52144-4-b5pPuOcMJz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52144-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52144 --- Comment #8 from chrbr at gcc dot gnu.org --- Author: chrbr Date: Mon Jun 22 07:32:15 2015 New Revision: 224721 URL: https://gcc.gnu.org/viewcvs?rev=224721&root=gcc&view=rev Log: Add -mflip-thumb for testing. PR target/52144n * config/arm/arm.c (add_attribute, arm_insert_attributes): New functions (TARGET_INSERT_ATTRIBUTES): Define. (thumb_flipper): New var. * config/arm/arm.opt (-mflip-thumb): New switch. PR target/52144 * gcc.target/arm/flip-thumb.c: New test. Added: trunk/gcc/testsuite/gcc.target/arm/flip-thumb.c Modified: trunk/gcc/ChangeLog trunk/gcc/config/arm/arm.c trunk/gcc/config/arm/arm.opt trunk/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2015-06-22 7:32 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-06 23:02 [Bug target/52144] New: " rafael.carre at gmail dot com 2012-02-06 23:03 ` [Bug target/52144] " pinskia at gcc dot gnu.org 2015-05-20 12:59 ` chrbr at gcc dot gnu.org 2015-05-20 13:13 ` chrbr at gcc dot gnu.org 2015-05-26 14:06 ` chrbr at gcc dot gnu.org 2015-06-10 7:51 ` chrbr at gcc dot gnu.org 2015-06-11 8:51 ` chrbr at gcc dot gnu.org 2015-06-19 6:59 ` chrbr at gcc dot gnu.org 2015-06-22 7:32 ` chrbr at gcc dot gnu.org [this message] 2015-06-22 8:22 ` chrbr at gcc dot gnu.org 2015-07-07 7:56 ` chrbr at gcc dot gnu.org 2015-09-15 13:43 ` chrbr 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-52144-4-b5pPuOcMJz@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).