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]

Avoid generating useless range info


Hi!

As discovered in my range class work, we seem to generate a significant amount of useless range info out of VRP.

Is there any reason why we can't avoid generating any range info that spans the entire domain, and yet contains nothing in the non-zero bitmask?

The attached patch passes bootstrap, and the one regression it causes is because now the -Walloca-larger-than= pass is better able to determine that there is no range information at all, and the testcase is unbounded. So...win, win.

OK for trunk?

Aldy

Attachment: curr
Description: Text document


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