[Bug middle-end/29782] Incorrect inlining failure

2007-04-08 Thread pinskia at gcc dot gnu dot org
--- Comment #6 from pinskia at gcc dot gnu dot org 2007-04-08 23:46 --- No real testcase in over 3 months so closing. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added ---

[Bug middle-end/29782] Incorrect inlining failure

2006-11-09 Thread pinskia at gcc dot gnu dot org
--- Comment #5 from pinskia at gcc dot gnu dot org 2006-11-09 17:31 --- Can you give your full testcase as right now the above testcases don't show what your code looks like and why we are reaching the large-function-growth limit. -- pinskia at gcc dot gnu dot org changed:

[Bug middle-end/29782] Incorrect inlining failure

2006-11-09 Thread takis at issaris dot org
--- Comment #4 from takis at issaris dot org 2006-11-09 17:28 --- (In reply to comment #3) > It has a heuristic to tell the result in code-size difference. Of course no > heuristic is perfect - see tree-inline.c:estimate_num_insns(). Ofcourse! Thanks for your reply! So, I guess that if

[Bug middle-end/29782] Incorrect inlining failure

2006-11-09 Thread rguenth at gcc dot gnu dot org
--- Comment #3 from rguenth at gcc dot gnu dot org 2006-11-09 17:10 --- It has a heuristic to tell the result in code-size difference. Of course no heuristic is perfect - see tree-inline.c:estimate_num_insns(). -- rguenth at gcc dot gnu dot org changed: What|Removed