[Bug tree-optimization/91663] split function can be re-inlined, leaving bad stack trace

[ian at airs dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91663

Ian Lance Taylor  changed:

   What|Removed |Added

 Status|WAITING |NEW

--- Comment #3 from Ian Lance Taylor  ---
I still see the problem with near-tip GCC.  Is there any reason to think that
this problem is fixed?

(Note that I'm reporting what I consider to be a bug in the C compiler.  The
patch attached to this PR is the Go frontend working around the problem in the
middle-end.  It's not a fix for the bug.)

[Bug tree-optimization/91663] split function can be re-inlined, leaving bad stack trace

[marxin at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91663

Martin Liška  changed:

   What|Removed |Added

 Status|UNCONFIRMED |WAITING
   Last reconfirmed||2020-01-29
 CC||marxin at gcc dot gnu.org
 Ever confirmed|0   |1

--- Comment #2 from Martin Liška  ---
@Ian: Can we close this?

[Bug tree-optimization/91663] split function can be re-inlined, leaving bad stack trace

[ian at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91663

--- Comment #1 from ian at gcc dot gnu.org  ---
Author: ian
Date: Thu Sep  5 04:12:30 2019
New Revision: 275396

URL: https://gcc.gnu.org/viewcvs?rev=275396=gcc=rev
Log:
PR tree-optimization/91663
* go-lang.c (go_langhook_post_options): Clear
flag_partial_inlining.

Modified:
trunk/gcc/go/ChangeLog
trunk/gcc/go/go-lang.c