Another shot at fixing the issues with (constant) struct literals and their addresses. See DMD2682, #218, #324. The idea is to separate the notion of const from 'this variable can always be replaced with its initializer' in the frontend. To do that, I introduced Declaration::isSameAsInitializer, which is overridden in VarDeclaration to return false for constants that have a struct literal initializer. So {{{ const S s = S(5); void foo() { auto ps = &s; } // is no longer replaced by void foo() { auto ps = &(S(5)); } }}} To make taking the address of a struct constant with a struct-initializer outside of function scope possible, I made sure that AddrExp::optimize doesn't try to run the argument's optimization with WANTinterpret - that'd again replace the constant with a struct literal temporary.

#!/bin/bash

HOST_TARGET=$1

[ "$HOST_TARGET" = "" ] && exit 1

REST=`echo $HOST_TARGET   | sed -e 's/[a-zA-Z0-9_]*\(\-.*\)/\1/'`
X86=`echo $HOST_TARGET    | sed -e 's/\(i[3-9]86\)\-.*/\1/'`
X86_64=`echo $HOST_TARGET | sed -e 's/\(x86_64\)\-.*/\1/'`

ALT=
if [ "$X86_64" != "$HOST_TARGET" ]; then
    ALT="i686$REST"

elif [ "$X86" != "$HOST_TARGET" ]; then
    ALT="x86_64$REST"
fi

echo $ALT