This is the mail archive of the gcc@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] | |
Thanks for the quick response. As it turns out, the libcall issue will
soon be gone, as bonzini will be deleting them. We have finally
overcome that issue.
I believe that what i am proposing is actually currently called (or at least related to) factored use def chains,
Ian is right, subregs were a problem (and strict_low_part). I don't recall offhand if it was "normal" subregs or paradoxicals (or both) that caused pain.
I haven't looked at the PR in question, but you could probably punt SUBREGs and get the benefits you want for real code on most ports. Yes, someone can (and probably will) contrive an example which does the same thing as your problem PR, but which is littered with SUBREGs in all the "right" places. But the question I think we have to ask at that point is whether or not such code is something we absolutely have to worry about from a compile-time or optimization standpoint.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |