This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: -ftree-check for review


I wrote:
> >You write: "Note that patterns are tried only on the top level of a
> >statement."  And later you write "for example the statement pattern
> >
> > @code{"gets (%_)" or "%_ = gets (%_)"}
> >
> >matches any call to
> > @code{gets ()}.
> >
> >But the gets result might be passed straight to another function:
> >
> >    f(gets(arglist));
> >
> >presumably the rule would not match in this case, right?

On Wed, Apr 18, 2007 at 10:00:35AM -0400, Sebastian Pop wrote:
> This should be matched as we're doing the pattern matching at the
> gimple level.
> The documentation should be improved to be more precise.

OK.  Unfortunately it's a bit tricky for the user who doesn't know GCC
internals to understand the consequences of the fact that the matching
is being run on gimple, and might wonder why a pattern with two operators
never matches.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]