public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/59289] [ARM] regression on unsigned-extend-2.c Date: Fri, 29 Nov 2013 15:19:00 -0000 [thread overview] Message-ID: <bug-59289-4-PSOd2qFdiT@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59289-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59289 --- Comment #2 from ktkachov at gcc dot gnu.org --- Author: ktkachov Date: Fri Nov 29 15:19:34 2013 New Revision: 205529 URL: http://gcc.gnu.org/viewcvs?rev=205529&root=gcc&view=rev Log: 2013-11-29 Kyrylo Tkachov <kyrylo.tkachov@arm.com> PR target/59289 * config/arm/arm.c (cortexa15_extra_costs): Adjust costs. Modified: trunk/gcc/ChangeLog trunk/gcc/config/arm/arm.c
next prev parent reply other threads:[~2013-11-29 15:19 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-11-25 16:07 [Bug target/59289] New: " christophe.lyon at st dot com 2013-11-26 9:10 ` [Bug target/59289] [4.9 Regression][ARM] " rguenth at gcc dot gnu.org 2013-11-27 9:57 ` [Bug target/59289] [ARM] " ktkachov at gcc dot gnu.org 2013-11-29 15:19 ` ktkachov at gcc dot gnu.org [this message] 2013-11-29 15:20 ` ktkachov 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-59289-4-PSOd2qFdiT@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).