From 16667e0626dfa6e56cc423405b0295d5a568b78e Mon Sep 17 00:00:00 2001 From: Hans Wennborg Date: Mon, 25 Feb 2019 16:06:37 +0000 Subject: [PATCH] ReleaseNotes: drop mention of -ftrivial-auto-var-init=zero llvm-svn: 354794 --- clang/docs/ReleaseNotes.rst | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/clang/docs/ReleaseNotes.rst b/clang/docs/ReleaseNotes.rst index 4c593977e2c32..54a7a4c1b976c 100644 --- a/clang/docs/ReleaseNotes.rst +++ b/clang/docs/ReleaseNotes.rst @@ -41,7 +41,7 @@ Major New Features example, due to renaming a class or namespace). See the :ref:`UsersManual ` for details. -- Clang has new options to initialize automatic variables with either a pattern or with zeroes. The default is still that automatic variables are uninitialized. This isn't meant to change the semantics of C and C++. Rather, it's meant to be a last resort when programmers inadvertently have some undefined behavior in their code. These options aim to make undefined behavior hurt less, which security-minded people will be very happy about. Notably, this means that there's no inadvertent information leak when: +- Clang has new options to initialize automatic variables with a pattern. The default is still that automatic variables are uninitialized. This isn't meant to change the semantics of C and C++. Rather, it's meant to be a last resort when programmers inadvertently have some undefined behavior in their code. These options aim to make undefined behavior hurt less, which security-minded people will be very happy about. Notably, this means that there's no inadvertent information leak when: * The compiler re-uses stack slots, and a value is used uninitialized. @@ -65,8 +65,6 @@ Major New Features * ``-ftrivial-auto-var-init=pattern`` - * ``-ftrivial-auto-var-init=zero`` ``-enable-trivial-auto-var-init-zero-knowing-it-will-be-removed-from-clang`` - There is also a new attribute to request a variable to not be initialized, mainly to disable initialization of large stack arrays when deemed too expensive: * ``int dont_initialize_me __attribute((uninitialized));``