[Bug tree-optimization/53385] [4.8 Regression] "Error: operand out of range" after changes for LSHIFT_EXPR in vrp.c

2012-05-18 Thread jakub at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53385 --- Comment #10 from Jakub Jelinek 2012-05-18 08:24:40 UTC --- So I think you could do: case 'W': /* MB value for a PowerPC64 rldic operand. */ i = clz_hwi (GET_CODE (x) == CONST_INT ? INTVAL (x) : CONST_DOUBLE

[Bug tree-optimization/53385] [4.8 Regression] "Error: operand out of range" after changes for LSHIFT_EXPR in vrp.c

2012-05-18 Thread jakub at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53385 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment #9 f

[Bug tree-optimization/53385] [4.8 Regression] "Error: operand out of range" after changes for LSHIFT_EXPR in vrp.c

2012-05-17 Thread wschmidt at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53385 --- Comment #8 from William J. Schmidt 2012-05-18 03:42:46 UTC --- I suspect you're right. I'll have a look at it tomorrow.

[Bug tree-optimization/53385] [4.8 Regression] "Error: operand out of range" after changes for LSHIFT_EXPR in vrp.c

2012-05-17 Thread glisse at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53385 --- Comment #7 from Marc Glisse 2012-05-17 21:34:23 UTC --- Created attachment 27429 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27429 patch I believe you need something like this completely untested patch to avoid undefined behavior wit

[Bug tree-optimization/53385] [4.8 Regression] "Error: operand out of range" after changes for LSHIFT_EXPR in vrp.c

2012-05-17 Thread dje at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53385 David Edelsohn changed: What|Removed |Added Keywords||wrong-code Target Milestone|---