Sender: ghh AT mail DOT mtk DOT nao DOT ac DOT jp
Message-ID: <38BCDFC0.8AA4C88B@nao.ac.jp>
Date: Wed, 01 Mar 2000 18:15:44 +0900
From: Gerhard Heinzel <gerhard DOT heinzel AT nao DOT ac DOT jp>
Organization: National Astronomical Observatory, Mitaka, Tokyo, Japan
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.0.36 i686)
X-Accept-Language: de, en, ja, zh-CN
MIME-Version: 1.0
To: Tuukka Toivonen <tutoivon AT mail DOT student DOT oulu DOT fi>, pgcc AT delorie DOT com
Subject: Re: inline optimizer bug
References: <Pine DOT SGI DOT 4 DOT 21 DOT 0003011055380 DOT 14017478-100000 AT paju DOT oulu DOT fi>
Content-Type: text/plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit
Reply-To: pgcc AT delorie DOT com

Tuukka Toivonen wrote:
> 
> > I use
> > pgcc-2.95.2 19991024 (release)
> 
> Sorry I can't help you. But I wonder if you have noticed the
> "complex" datatype in GCC? If you want to write ANSI C, you can't use it,
> but if it's ok to use GCC only, it makes complex calculations much easier.
> 
> __complex__ double x;
> 
> main() {
>         x = 1.0 + 3.0i;
>         x = x / (2.0 - 2.0i);
>         printf("%f + %fi\n", __real__ x, __imag__ x);
> }
> 

Thanks, I know about it.

The piece of code that caused the optimizer bug
came from a "f2c" 'ed FORTRAN program which
defines "complex" differently, hence
my own definition of "mycomplex".

But I think this has nothing to do
with the optimizer bug, which, by the way,
seems NOT to present in the mainline gcc 2.95.2

Gerhard



-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
 Gerhard Heinzel                   e-mail: gerhard DOT heinzel AT nao DOT ac DOT jp
 Space-Time Astronomy Section, 
 National Astronomical Observatory, 2-21-1 Ohsawa, Mitaka,
 Tokyo 181-8588, Japan,    FAX: 81+422-34-3793,  Tel. 81+422-34-3618
 http://tamago.mtk.nao.ac.jp/   
http://users.cybercity.dk/~cis6614/Lucia 
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --