aboutsummaryrefslogtreecommitdiff
path: root/gcc/doc
diff options
context:
space:
mode:
authorJason Merrill <jason@redhat.com>2016-02-24 10:18:04 -0500
committerJason Merrill <jason@gcc.gnu.org>2016-02-24 10:18:04 -0500
commita021961c055d4d056d8bd7875a93c5e53450afd9 (patch)
tree66d1ebef423cc0ae9ed52f94ce534df41312b6f8 /gcc/doc
parent28577b86833bdb2e5241790f233fd2503ab4f880 (diff)
downloadgcc-a021961c055d4d056d8bd7875a93c5e53450afd9.zip
gcc-a021961c055d4d056d8bd7875a93c5e53450afd9.tar.gz
gcc-a021961c055d4d056d8bd7875a93c5e53450afd9.tar.bz2
Add -flifetime-dse=1.
gcc/ * common.opt (flifetime-dse): Add -flifetime-dse=1. gcc/cp/ * decl.c (start_preparsed_function): Condition ctor clobber on flag_lifetime_dse > 1. From-SVN: r233672
Diffstat (limited to 'gcc/doc')
-rw-r--r--gcc/doc/invoke.texi5
1 files changed, 4 insertions, 1 deletions
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index 9ca3793..b8b2e70 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -6809,7 +6809,10 @@ value, and any changes during the lifetime of the object are dead when
the object is destroyed. Normally dead store elimination will take
advantage of this; if your code relies on the value of the object
storage persisting beyond the lifetime of the object, you can use this
-flag to disable this optimization.
+flag to disable this optimization. To preserve stores before the
+constructor starts (e.g. because your operator new clears the object
+storage) but still treat the object as dead after the destructor you,
+can use -flifetime-dse=1.
@item -flive-range-shrinkage
@opindex flive-range-shrinkage