public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Bingfeng Mei" <bmei@broadcom.com>
To: ddmetro <puzzlesdj@gmail.com>, 	"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: RE: help on - adding a new pass to gcc
Date: Tue, 10 Nov 2009 16:37:00 -0000	[thread overview]
Message-ID: <7FB04A5C213E9943A72EE127DB74F0AD93CCCB4031@SJEXCHCCR02.corp.ad.broadcom.com> (raw)
In-Reply-To: <26286452.post@talk.nabble.com>

Did you add your new object file to OBJS-common list in Makefile.in? 

Bingfeng



> -----Original Message-----
> From: gcc-owner@gcc.gnu.org [mailto:gcc-owner@gcc.gnu.org] On 
> Behalf Of ddmetro
> Sent: 10 November 2009 16:25
> To: gcc@gcc.gnu.org
> Subject: help on - adding a new pass to gcc
> 
> 
> Hi All,
>          We are adding a new pass for - structural hazard 
> optimization - in
> gcc.
>          We have added a rtl_opt_pass variable(pass_sched3) 
> declaration in
> tree-pass.h and defined the same in a new file - sched-by-category.c
>          We then added a target in gcc/Makefile.in, as follows:
> sched-by-category.o : sched-by-category.c $(CONFIG_H) $(SYSTEM_H)
> coretypes.h $(TM_H) \
>    $(RTL_H) $(SCHED_INT_H) $(REGS_H) hard-reg-set.h 
> $(FLAGS_H) insn-config.h
> \
>    $(FUNCTION_H) $(INSN_ATTR_H) $(TOPLEV_H) $(RECOG_H) 
> except.h $(PARAMS_H)
> \
>    $(TM_P_H) $(TARGET_H) $(CFGLAYOUT_H) $(TIMEVAR_H) tree-pass.h  \
>    $(DBGCNT_H)
> 
>          We are getting an error in passes.c - undefined reference to
> 'pass_sched3'
>          Kindly guide us as to what is wrong in our approach 
> of adding a new
> file to gcc build.
> 
> Thanking You,
>   Dhiraj.
> -- 
> View this message in context: 
> http://old.nabble.com/help-on---adding-a-new-pass-to-gcc-tp262
> 86452p26286452.html
> Sent from the gcc - Dev mailing list archive at Nabble.com.
> 
> 
> 

  parent reply	other threads:[~2009-11-10 16:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-10 16:25 ddmetro
2009-11-10 16:36 ` Andrew Pinski
2009-11-10 16:37 ` Bingfeng Mei [this message]
2009-11-10 16:45 ` Basile STARYNKEVITCH

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=7FB04A5C213E9943A72EE127DB74F0AD93CCCB4031@SJEXCHCCR02.corp.ad.broadcom.com \
    --to=bmei@broadcom.com \
    --cc=gcc@gcc.gnu.org \
    --cc=puzzlesdj@gmail.com \
    /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).