public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
* Re: Code Flow for RTL generation
       [not found]   ` <f69849430606150558q21486596laaa1be48e914737b@mail.gmail.com>
@ 2006-06-15 13:03     ` Andrew Haley
  0 siblings, 0 replies; only message in thread
From: Andrew Haley @ 2006-06-15 13:03 UTC (permalink / raw)
  To: kernel coder; +Cc: gcc-help

[ 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.

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2006-06-15 13:03 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <f69849430606150336y63ae84daic00aa895753ba3e4@mail.gmail.com>
     [not found] ` <17553.14587.997856.674073@dell.pink>
     [not found]   ` <f69849430606150558q21486596laaa1be48e914737b@mail.gmail.com>
2006-06-15 13:03     ` Code Flow for RTL generation Andrew Haley

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).