From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <b07db7c1b6104c9e725b396045495242@collyer.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] how to avoid a memset() optimization
From: Geoff Collyer <geoff@collyer.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Tue, 12 Nov 2002 22:52:25 -0800
Topicbox-Message-UUID: 1c81477e-eacb-11e9-9e20-41e7f4b1d025

When I'm stuck with using gcc, I invoke it with this script:

#!/bin/sh
# agcc - invoke gcc in ansi mode
# the --writable-strings is for pre-ansi programs like some versions of mk
exec gcc -ansi -pipe -fvolatile --writable-strings "$@"

-fvolatile makes gcc treat all data as if declared volatile.  I
sometimes add (usually to the ?akefile) `-Dconst=' to deal with const
poisoning.

gcc(1) is a treasure hunt; there's all sorts of stuff buried in there.