Skip to content

-funfolding-update-in-place badly documented

The documentation for -funfolding-update-in-place implies it takes a numeric argument:

-funfolding-update-in-place=n

Switches on an experimental "optimisation". Switching it on makes the compiler a little keener to inline a function that returns a constructor, if the context is that of a thunk.

But in fact it does not. Either the documentation is wrong or the implementation has a bug, as compiling with -funfoling-update-in-place=10 gives an error that the flag is not recognized.

Trac metadata
Trac field Value
Version 6.8.1
Type Bug
TypeOfFailure OtherFailure
Priority normal
Resolution Unresolved
Component Compiler
Test case
Differential revisions
BlockedBy
Related
Blocking
CC
Operating system
Architecture
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information