From: Ye Joey <joey.ye.cc@gmail.com>
To: Bin Cheng <bin.cheng@arm.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH arm/embedded-4_7-branch]fix fialure of mtune option
Date: Thu, 06 Jun 2013 01:49:00 -0000 [thread overview]
Message-ID: <CAL0py27V9g4+7G-An8Z2que+oe8HBXNeymcK04sVj7C2dtiT3A@mail.gmail.com> (raw)
In-Reply-To: <51afea61.6687440a.6fd9.0027SMTPIN_ADDED_BROKEN@mx.google.com>
OK to embedded-4_7-branch.
Thanks,
Joey
On Thu, Jun 6, 2013 at 9:43 AM, Bin Cheng <bin.cheng@arm.com> wrote:
> Hi,
> This patch fixes failure of command "arm-none-eabi-gcc -O2 -mthumb
> -mtune=cortex-m4 ..." on arm/embedded-4_7-branch by removing the assertion
> in arm_cortex_v7m_branch_cost.
>
> Is it OK?
>
> Thanks.
>
> 2013-06-06 Bin Cheng <bin.cheng@arm.com>
>
> * config/arm/arm.c (arm_cortex_v7m_branch_cost): Remove assertion
> on TARGET_32BIT and TARGET_THUMB2.
next parent reply other threads:[~2013-06-06 1:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51afea61.6687440a.6fd9.0027SMTPIN_ADDED_BROKEN@mx.google.com>
2013-06-06 1:49 ` Ye Joey [this message]
2013-06-06 1:48 Bin Cheng
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=CAL0py27V9g4+7G-An8Z2que+oe8HBXNeymcK04sVj7C2dtiT3A@mail.gmail.com \
--to=joey.ye.cc@gmail.com \
--cc=bin.cheng@arm.com \
--cc=gcc-patches@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).