Skip to content
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.

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

Unreachable code warning on MSVC builds in test matrix #180

Closed
jeking3 opened this Issue Nov 11, 2018 · 1 comment

Comments

Projects
None yet
2 participants
@jeking3
Copy link
Contributor

jeking3 commented Nov 11, 2018

https://www.boost.org/development/tests/develop/output/teeks99-09-p-win2012R2-64on64-test-msvc-14-1-warnings.html#doc-example22

d:\teeks99-09\run\boost_root\boost\test\impl\test_tools.ipp(377) : warning C4702: unreachable code

Happens on most of the tests.

raffienficiaud added a commit that referenced this issue Jan 15, 2019

raffienficiaud added a commit that referenced this issue Feb 1, 2019

raffienficiaud added a commit that referenced this issue Feb 1, 2019

raffienficiaud added a commit that referenced this issue Feb 2, 2019

Merge branch 'topic/UBSAN-issues-fix' into next-internal
* topic/UBSAN-issues-fix:
  Disabling FPE tests under UBSAN
  Prevent sanitizer on specific function
  Visibility fixes
  Error in the definition of “set” in a test
  Disabling optimization example22/example23
  Change log GH-180
  GH-180: warning for unreachable return statement
  Check warning removal
  build folder
  Making the examples as part of the tests being run
  Example29: being able to save the pattern

raffienficiaud added a commit that referenced this issue Feb 2, 2019

Merge branch 'topic/UBSAN-issues-fix' into next-internal
* topic/UBSAN-issues-fix:
  Disabling FPE tests under UBSAN
  Prevent sanitizer on specific function
  Visibility fixes
  Error in the definition of “set” in a test
  Disabling optimization example22/example23
  Change log GH-180
  GH-180: warning for unreachable return statement
  Check warning removal
  build folder
  Making the examples as part of the tests being run
  Example29: being able to save the pattern
@raffienficiaud

This comment has been minimized.

Copy link
Member

raffienficiaud commented Feb 2, 2019

Resolved via aec7ebe and 775114e

@raffienficiaud raffienficiaud self-assigned this Feb 2, 2019

@raffienficiaud raffienficiaud added the 1.70 label Feb 8, 2019

@raffienficiaud raffienficiaud added this to the 1.70 milestone Feb 8, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.