ed/TimothyLottes.github.io
1
0
Fork 0
mirror of https://github.com/gomson/TimothyLottes.github.io.git synced 2026-08-04 14:48:49 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add files via upload

Browse Source
This commit is contained in:
TimothyLottes
2016-11-12 21:13:03 -05:00
committed by GitHub
parent 4b9f906393
commit 71606f5ff8
2 changed files with 23 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
20140809.html
+22
View File
@@ -0,0 +1,22 @@
<html><head><link rel="stylesheet" href="style.css"></head><body><div class="page">
<h1>20140809 - Strict Aliasing</h1>
<br>
<i>Strict aliasing from a different perspective.
Full disclosure,
for the most part at home I've moved on from C to my own language
which is similar to an assembler
running from a language similar to Color Forth.
So my bias is more towards performance and minimalism.</i><br>
<br>
When working in C, outside of work, I adopted labeling all pointers as either "restrict" or "volatile" (using the defines below to keep syntax tight). If needed reuse of a value read from a volatile pointer, it is read into a local variable. When working this way, strict aliasing makes no difference.<br>
<br>
<tt>
#define R_ restrict<br>
#define V_ volatile</tt><br>
</div></body></html>
index.html
+1
View File
@@ -183,6 +183,7 @@ and attempting to restore what I can from prior lost images.
<a href="20140819.html">20140819 - Scanlines</a><br>
<a href="20140816.html">20140816 - Vintage Programming</a><br>
<a href="20140814.html">20140814 - HRAA And Coverage and Related Topics</a><br>
<a href="20140809.html">20140809 - Strict Aliasing</a><br>
<br>
<a href="20140730.html">20140730 - Scanlines and Vintage TVs</a><br>
<a href="20140723.html">20140723 - Body Hacking Running on Oil</a><br>