public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "wschmidt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/53955] [4.8 Regression] Missing prototypes in i386.c, bootstrap failure with --disable-build-poststage1-with-cxx Date: Fri, 13 Jul 2012 22:33:00 -0000 [thread overview] Message-ID: <bug-53955-4-HOxlSLslza@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53955-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53955 --- Comment #3 from William J. Schmidt <wschmidt at gcc dot gnu.org> 2012-07-13 22:33:36 UTC --- Author: wschmidt Date: Fri Jul 13 22:33:31 2012 New Revision: 189473 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=189473 Log: 2012-07-13 Bill Schmidt <wschmidt@linux.ibm.com> PR bootstrap/53955 * config/spu/spu.c (spu_init_cost): Mark static. (spu_add_stmt_cost): Likewise. (spu_finish_cost): Likewise. (spu_destroy_cost_data): Likewise. * config/i386/i386.c (ix86_init_cost): Mark static. (ix86_add_stmt_cost): Likewise. (ix86_finish_cost): Likewise. (ix86_destroy_cost_data): Likewise. * config/rs6000/rs6000.c (rs6000_init_cost): Mark static. (rs6000_add_stmt_cost): Likewise. (rs6000_finish_cost): Likewise. (rs6000_destroy_cost_data): Likewise. Modified: trunk/gcc/ChangeLog trunk/gcc/config/i386/i386.c trunk/gcc/config/rs6000/rs6000.c trunk/gcc/config/spu/spu.c
next prev parent reply other threads:[~2012-07-13 22:33 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-07-13 17:00 [Bug bootstrap/53955] New: " tkoenig at gcc dot gnu.org 2012-07-13 17:01 ` [Bug bootstrap/53955] " tkoenig at gcc dot gnu.org 2012-07-13 17:05 ` steven at gcc dot gnu.org 2012-07-13 21:02 ` wschmidt at gcc dot gnu.org 2012-07-13 22:33 ` wschmidt at gcc dot gnu.org [this message] 2012-07-13 22:34 ` wschmidt 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-53955-4-HOxlSLslza@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).