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] |
The specific cases I've seen won't combine at the gimple level. For example, if you look at the H8, you need to have a post-inc memory operand which I really doubt we're going to ever expose at the gimple level.
If it's patterns we could combine at the GIMPLE level, it wouldn't be so silly to handle it there. Weren't you once one of the people talking about a tree-combine pass?
Again, I don't think the majority of the cases where 4->1 or 4->2 combinations occur are going to be anything that we'd expose that early in the pipeline.Or if this is a case the compiler could already expand from GIMPLE to good initial RTL (i.e. TER), that wouldn't be a silly place to put it either.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |