Remove trailing whitespaces

using trailing_whitespace_remover.sh

Author: aminya

ChangeLog.md

@@ -28,7 +28,7 @@ Current Trunk
 ------------------
 - `emscripten/vr.h` and other remnants of WebVR support removed. (#13210, which
   is a followup to #10460)
-- Stop overriding CMake default flags based on build type. This will 
+- Stop overriding CMake default flags based on build type. This will
   result in builds that are more like CMake does on other platforms. You
   may notice that `RelWithDebInfo` will now include debug info (it did not
   before, which appears to have been an error), and that `Release` will
@@ -216,7 +216,7 @@ Current Trunk
   is encountered. This makes the Emscripten program behave more like a native
   program where the OS would terminate the process and no further code can be
   executed when an unhandled exception (e.g. out-of-bounds memory access) happens.
-  Once the program aborts any exported function calls will fail with a "program 
+  Once the program aborts any exported function calls will fail with a "program
   has already aborted" exception to prevent calls into code with a potentially
   corrupted program state.
 - Use `__indirect_function_table` as the import name for the table, which is

LICENSE

@@ -57,7 +57,7 @@ the following conditions:
     Neither the names of Mozilla,
     nor the names of its contributors may be used to endorse
     or promote products derived from this Software without specific prior
-    written permission. 
+    written permission.
 
 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
 OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF

docs/packaging.md

@@ -6,7 +6,7 @@ linux distributions, or other downstream SDKs.
 
 Firstly, we provide an install script in `tools/install.py`.  This allows
 just the end-user parts of emscripten to be installed.  For example this avoids
-including the `tests/third_party` directory which is of that biggest parts 
+including the `tests/third_party` directory which is of that biggest parts
 of the source tree.
 
 If you prefer, you can use `make install` or `make dist` which invokes

site/source/conf.py

@@ -68,7 +68,7 @@
 
 
 #Build "Todo" notes into the source
-#todo_include_todos = 'True' 
+#todo_include_todos = 'True'
 
 # Add any paths that contain templates here, relative to this directory.
 templates_path = ['_templates']

site/source/docs/api_reference/Filesystem-API.rst

@@ -766,12 +766,12 @@ Paths
 .. js:function:: FS.analyzePath(path, dontResolveLastLink)
 
   Looks up the incoming path and returns an object containing information about
-  file stats and nodes. Built on top of ``FS.lookupPath`` and provides more 
-  information about given path and its parent. If any error occurs it won't 
+  file stats and nodes. Built on top of ``FS.lookupPath`` and provides more
+  information about given path and its parent. If any error occurs it won't
   throw but returns an ``error`` property.
 
   :param string path: The incoming path.
-  :param boolean dontResolveLastLink: If true, don't follow the last component 
+  :param boolean dontResolveLastLink: If true, don't follow the last component
     if it is a symlink.
 
   :returns: an object with the format:
@@ -780,13 +780,13 @@ Paths
 
       {
         isRoot: boolean,
-        exists: boolean, 
-        error: Error, 
-        name: string, 
-        path: resolved_path, 
+        exists: boolean,
+        error: Error,
+        name: string,
+        path: resolved_path,
         object: resolved_node,
-        parentExists: boolean, 
-        parentPath: resolved_parent_path, 
+        parentExists: boolean,
+        parentPath: resolved_parent_path,
         parentObject: resolved_parent_node
       }
 

site/source/docs/building_from_source/configuring_emscripten_settings.rst

@@ -18,15 +18,15 @@ Creating the compiler configuration file
 The settings file is created the first time a user runs :ref:`emcc <emccdoc>` (or any of the other Emscripten tools):
 
 1. Navigate to the directory where you cloned the Emscripten repository.
-2. Enter the command: 
+2. Enter the command:
 
 	::
-	
+
 		./emcc --help
 
 	You should get a ``Welcome to Emscripten!`` message. Behind the scenes, Emscripten generates a file called ``.emscripten`` in your home folder.
-	
-	
+
+
 Emscripten makes a "best guess" at the correct locations for tools and updates the file appropriately. Where possible it will look for "system" apps (like Python and Java).
 
 In most cases it is necessary to edit the generated file and modify at least the
@@ -57,28 +57,28 @@ Compiler configuration file-format
 The file simply assigns paths to a number of *variables* representing the main tools used by Emscripten. For example, if the user installed python to the **C:/Python27/** directory, then the file might have the line: ::
 
 	PYTHON = 'C:\\Python38\\python.exe'
-	
+
 
 The default *emcc* configuration file often gets the paths from environment variables if defined. If no variable is defined the system will also attempt to find "system executables". For example:  ::
 
 	PYTHON = os.path.expanduser(os.getenv('PYTHON', 'C:\\Python38\\python.exe'))
 
-You can find out the other variable names from the default *.emscripten* file or the :ref:`example here <compiler-configuration-file>`. 
+You can find out the other variable names from the default *.emscripten* file or the :ref:`example here <compiler-configuration-file>`.
 
 Editing the compiler configuration file
 =======================================
 
 The compiler configuration file can be edited with the text editor of your choice. As stated above, most default settings are likely to be correct. If you're building manually from source, you are most likely to have to update the variable ``LLVM_ROOT``
 
-		
+
 #. Edit the variable ``LLVM_ROOT`` to point to the directory where you built the LLVM binaries, such as:
-   
+
 	::
-   
+
 		LLVM_ROOT = os.path.expanduser(os.getenv('LLVM', '/home/ubuntu/a-path/llvm/build/bin'))
 
 	.. note:: Use forward slashes!
 
 .. comment .. The settings are now correct in the configuration file, but the paths and environment variables are not set in the command prompt/terminal. **HamishW** Follow up with Jukka on this.
- 
+
 After setting those paths, run ``emcc`` again. It should again perform the sanity checks to test the specified paths. There are further validation tests available at :ref:`verifying-the-emscripten-environment`.

site/source/docs/compiling/Building-Projects.rst

@@ -304,7 +304,7 @@ The :ref:`Tutorial` showed how :ref:`emcc <emccdoc>` can be used to compile sing
   ./emcc src1.o src2.o -r -o combined.o
 
   # Combine two object files into library file
-  ./emar rcs libfoo.a src1.o src2.o 
+  ./emar rcs libfoo.a src1.o src2.o
 
 
 In addition to the capabilities it shares with *gcc*, *emcc* supports options to optimize code, control what debug information is emitted, generate HTML and other output formats, etc. These options are documented in the :ref:`emcc tool reference <emccdoc>` (``./emcc --help`` on the command line).

site/source/docs/contributing/developers_guide.rst

@@ -30,7 +30,7 @@ binaries with a checkout of the core Emscripten repository, simply by calling
 ``emcc.py`` from that checkout, and it will use the binaries from the emsdk.
 
 If you do want to contribute to LLVM or Binaryen, or to test modifications
-to them, you can 
+to them, you can
 :ref:`build them from source <installing-from-source>`.
 
 Repositories and branches of interest

site/source/docs/getting_started/FAQ.rst

@@ -483,7 +483,7 @@ strings, so it accepts ``[a]`` or ``[a,b]`` etc.).
 
 
 Why do I get a Python ``SyntaxError: invalid syntax`` on ``file=..`` or on a string starting with ``f'..'``?
-============================================================================================================ 
+============================================================================================================
 
 Emscripten requires a recent-enough version of Python. An older Python version,
 like ``2.*``, will not support the print statement by default, so it will error on

site/source/docs/getting_started/downloads.rst

@@ -70,7 +70,7 @@ There are also "tip-of-tree builds", which are the very latest code that passes
 
   ::
 
-    # Get a tip-of-tree 
+    # Get a tip-of-tree
     ./emsdk install tot
 
 (In the above examples we installed the various targets; remember to also ``activate`` them as in the full example from earlier.)