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.

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

Jump to bottom

Add CC for portability is reliability #2076

Merged
merged 4 commits into from
May 13, 2024
Merged

Add CC for portability is reliability #2076

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
606460a
add cc
markcmiller86 Apr 21, 2024
d19832d
Adjust paragraph breaking
markcmiller86 May 2, 2024
13bcaa9
update publish date
rinkug May 13, 2024
c2affe7
Update PortabilityIsReliability.md
rinkug May 13, 2024
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
31 changes: 31 additions & 0 deletions CuratedContent/PortabilityIsReliability.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,31 @@
# Portability is reliability
<!--deck text start-->
Portability can be a means to an end and does not need to be not an end in and of itself.
<!--deck text end-->

#### Contributed by [Mark C. Miller](https://github.com/markcmiller86 "Mark C. Miller GitHub Profile")
#### Publication date: March 7, 2024

Resource information | Details
:--- | :---
Article Title | [Portability is Reliability](https://evan.nemerson.com/2021/05/04/portability-is-reliability/)
Author | [Evan Nemerson](https://github.com/nemequ)
Focus | Testing, Software sustainability, Reliability

In this article, the author highlights a number of ways in which compiling and running code with different compilers and architectures improves the quality and reliability of the code.
Different compilers are better at manifesting and catching different kinds of issues.
The article mentions, for example, that clang often catches a larger set of issues than does gcc.
It also explains that, in spite of challenges in using MSVC, one of the great advantages of compiling with it may be its static analyzer which, in the author's opinion, may be the best part of the MSVC compiler.
The article also explains the importance of doing development with as many compiler warnings enabled as possible using flags such as `-Wall`, `-Wextra`, `-Weverything` and `-Werror` or `/W4` for MSVC.
By including compilation with strict warningns enabled and with different compilers in CI, it is possible to catch and prevent a lot of issues before they make it into a committed version of the code.

The author also explains the value in using different architectures such as armv7 (which is more strict about aliasing violations) or s390x (which is a big endian architecture) to also help shake out issues with code.

Using various available compilers and architectures (as containers for example) on a code base is a great way to take advantage of some available automation to find and prevent issues from creeping into a code base.

<!---
Publish: yes
Topics: Testing, Software sustainability, Reliability
Pinned: no
RSS update: 2024-02-07
--->
Loading