This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: Code Flow for RTL generation
- From: Andrew Haley <aph at redhat dot com>
- To: "kernel coder" <lhrkernelcoder at gmail dot com>
- Cc: gcc-help at gcc dot gnu dot org
- Date: Thu, 15 Jun 2006 14:03:21 +0100
- Subject: Re: Code Flow for RTL generation
- References: <f69849430606150336y63ae84daic00aa895753ba3e4@mail.gmail.com> <17553.14587.997856.674073@dell.pink> <f69849430606150558q21486596laaa1be48e914737b@mail.gmail.com>
[ Redirected to gcc-help@. This tutorial-level exchange isn't
appropriate for gcc@. ]
Please don't top-post.
kernel coder writes:
> is there any way in gdb to step backward.
No, there isn't. If you want to know where the routines were called
from go up.
Andrew.
> On 6/15/06, Andrew Haley <aph@redhat.com> wrote:
> > kernel coder writes:
> > > hi,
> > > I'm trying to figure out the code flow of gcc.But i'm not been
> > > able to locate the location at which an expression is compared with
> > > pattern given in XXXX.md file.
> > >
> > > I think XXXX.md file is resposible fo generation of emit-insn.c
> > > file.But again at which point the functions in emit-insn.c file are
> > > called for generation of RTL file.
> > >
> > > Please tell me where in code the pattern matching is done for RTL
> > > generation.
> >
> > Run cc1 in gdb. Put a breakpoint on make_insn_raw. Go up from that
> > point to find the caller. You'll find that GEN_foo routines are
> > called from a number of places, in particular the expander.