public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "nickc at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/49403] v850e-elf: incompatible pointer type (near initialization for ‘targetm.memory_move_cost’) Date: Tue, 14 Jun 2011 15:31:00 -0000 [thread overview] Message-ID: <bug-49403-4-qF0NYOmvXz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49403-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49403 --- Comment #1 from Nick Clifton <nickc at gcc dot gnu.org> 2011-06-14 15:30:15 UTC --- Author: nickc Date: Tue Jun 14 15:30:05 2011 New Revision: 175030 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=175030 Log: PR target/49403 * config/v850/v850.c (v850_memory_move_cost): Add reg_class_t parameter. PR target/49402 * config.gcc(v850*-*-*): Avoid duplication of v850.opt. Modified: trunk/gcc/ChangeLog trunk/gcc/config.gcc trunk/gcc/config/v850/v850.c
next prev parent reply other threads:[~2011-06-14 15:31 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-06-14 9:20 [Bug target/49403] New: " amylaar at gcc dot gnu.org 2011-06-14 15:31 ` nickc at gcc dot gnu.org [this message] 2011-06-14 15:32 ` [Bug target/49403] " nickc at redhat dot com 2012-03-05 22:46 ` amylaar 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-49403-4-qF0NYOmvXz@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).