Skip to content

Repo sync for protected CLA branch #3052

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Mar 26, 2021
Merged

Repo sync for protected CLA branch #3052

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
a7657ab
Fix bolding
Mar 23, 2021
d5a1fc8
Merge pull request #3455 from stwish-msft/patch-3
PRMerger8 Mar 23, 2021
2e33fc5
Merge pull request #3456 from MicrosoftDocs/FromPublicMasterBranch
PRMerger20 Mar 24, 2021
d775eac
Merge pull request #3457 from MicrosoftDocs/master
Taojunshen Mar 24, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/porting/visual-cpp-what-s-new-2003-through-2015.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1008,7 +1008,7 @@ Although these differences can affect your source code or other build artifacts,
}
```

- ** Removal of `pow(T, int)` unrolling optimization **
- **Removal of `pow(T, int)` unrolling optimization**

Previous versions of the C++ standard library defined a `pow(T, int)` function template that would unroll a `pow` function call into a series of multiplication operations. This technique would accrue a large amount of inaccuracy due to the nature of floating point operations, causing end results that could be significantly inaccurate. In Visual Studio 2015 Update 1, this behavior was removed to avoid unintentional loss of accuracy when using the `pow` function. However, this version of `pow` was much faster than the correct calculation. If this change causes a significant performance regression and your project does not require precise floating point results (for example, your project already compiles with /fp:fast), consider replacing calls to `pow` with this workaround function:

Expand Down