From mboxrd@z Thu Jan  1 00:00:00 1970
From: Mike Stump <mrs@windriver.com>
To: dan@cgsoftware.com, mark@codesourcery.com
Cc: gcc@gcc.gnu.org, wilson@cygnus.com
Subject: Re: Bootstrap failure of gcc-ss-20010409 in ia64
Date: Tue, 17 Apr 2001 18:12:00 -0000
Message-id: <200104180111.SAA26807@kankakee.wrs.com>
X-SW-Source: 2001-04/msg00839.html

> To: Mark Mitchell <mark@codesourcery.com>
> Cc: wilson@cygnus.com, gcc@gcc.gnu.org
> From: Daniel Berlin <dan@cgsoftware.com>
> Date: 17 Apr 2001 19:16:23 -0400

> > The debugger can't really be expected to print out information
> > about the values of variables that were optimized away, for
> > example.
> This is the only case that is "unattainable".

Actually, if you can make it spit out 5, when a user says p i, when
the software has a { const int i = 5; } then I don't see why you can't
mostly solve the last as well.  In fact, I thought dwarf 2 had enough
guts to do this.

If not that, maybe p i with { enum { i = 5 }; }?