From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 Date: Mon, 15 Jun 2015 09:21:56 +0100 Message-ID: From: Charles Forsyth To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=089e013c673ca6e4b105188a26d3 Subject: [9fans] make passive aggressive gcc Topicbox-Message-UUID: 58919878-ead9-11e9-9d60-3106f5b1d025 --089e013c673ca6e4b105188a26d3 Content-Type: text/plain; charset=UTF-8 If you're using gcc 4.8.2 to compile ... anything, really ... but certainly Plan 9 or Inferno components, and those use for loops with arrays, be sure to include the compilation options -fno-strict-aliasing\ -fno-aggressive-loop-optimizations\ and it will save you some time and effort. It will save compilation time (not that you'll notice with that sluggard) because it won't fuss even more with your program, and it will save effort, because you won't have to debug simple loops that have bounds changed, are removed completely, or otherwise wrecked. You can find discussions of it elsewhere (which is how I found compiler options to stop it). I'd forgotten all about it until it surfaced again. --089e013c673ca6e4b105188a26d3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
If you're using gcc 4.8.2 to compile ... anything, rea= lly ... but certainly Plan 9 or Inferno components,
and those use for l= oops with arrays, be sure to include the compilation options
= -fno-strict-aliasing\
-fno-aggressiv= e-loop-optimizations\
and it will save you some time and ef= fort.
It will save compilation time (not that you'll notice w= ith that sluggard) because it won't
fuss even more with your = program, and it will save effort, because you won't have
to d= ebug simple loops that have bounds changed, are removed completely, or othe= rwise wrecked.
You can find discussions of it elsewhere (which is= how I found compiler options to stop it).
I'd fo= rgotten all about it until it surfaced again.

--089e013c673ca6e4b105188a26d3--