This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: PATCH: Loop to builtin call pass (builtinizer)
- From: Zdenek Dvorak <rakdver at kam dot mff dot cuni dot cz>
- To: Dorit Nuzman <DORIT at il dot ibm dot com>
- Cc: Tomas Bily <tbily at suse dot cz>, gcc-patches at gcc dot gnu dot org, tomby at ucw dot cz
- Date: Sun, 8 Jul 2007 17:07:06 +0200
- Subject: Re: PATCH: Loop to builtin call pass (builtinizer)
- References: <OFA3BFB0E1.0420E695-ONC2257312.002B5AD1-C2257312.002BBE47@il.ibm.com>
Hello,
> > Hi Dorit,
> >
> > I agree that a lot of analyzes in vectorizer and builtinizer are same
> > or very similar. So, I can try to merge it to vectorizer. I have first
> > few questions about it:
I would somewhat prefer not to merge the passes. After all, what they
do is substantially different, and it does not make much sense to me to
complicate vectorizer unnecessarily. Of course, if there is some amount
of same/similar code, share the appropriate functions.
The reason for merging vectorizer and builtinizer would be if there were
some interaction between them, i.e., if doing them at the same time
would enable us to optimize the code we cannot optimize now. Is that
the case? I do not think so -- it seems to me that running builtinizer
before vectorizer catches exactly the same amount of optimization
opportunities.
Zdenek