Andrey Belevantsev <[EMAIL PROTECTED]> writes:
> Is this intentional, or do we want to have 'return hash;' instead of
> 'return 0;' in all places when *do_not_record_p is set to 1? Is there
> a better hash_rtx somewhere, which I don't know about?
It should be fine to "return hash" instead of "re
Hello,
I would like to use some sort of hashing to speed up searching for an
insn in an availability set in the selective scheduler. It seems
natural using hash_rtx for this purpose. However, hash_rtx will not
hash any volatile subexpressions, returning 0 in this case. This is
fine by me,
