X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
From: Rugxulo <rugxulo AT gmail DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: GCC-4.4.0
Date: Mon, 25 May 2009 23:21:10 -0700 (PDT)
Organization: http://groups.google.com
Lines: 56
Message-ID: <782da8e7-6706-4626-a4e8-6469fcceb48f@m17g2000vbi.googlegroups.com>
References: <4A1A2B1C DOT 40503 AT iki DOT fi> <14171114-11cf-4aa5-bebe-ff3487aff924 AT o30g2000vbc DOT googlegroups DOT com> 
	<4A1A9564 DOT 1050305 AT iki DOT fi> <8ca6290b-d271-480c-8ef3-103d20aabf1e AT t21g2000yqi DOT googlegroups DOT com> 
	<4A1B8079 DOT 5030508 AT iki DOT fi>
NNTP-Posting-Host: 65.13.115.246
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Trace: posting.google.com 1243318870 26724 127.0.0.1 (26 May 2009 06:21:10 GMT)
X-Complaints-To: groups-abuse AT google DOT com
NNTP-Posting-Date: Tue, 26 May 2009 06:21:10 +0000 (UTC)
Complaints-To: groups-abuse AT google DOT com
Injection-Info: m17g2000vbi.googlegroups.com; posting-host=65.13.115.246; 
	posting-account=p5rsXQoAAAB8KPnVlgg9E_vlm2dvVhfO
User-Agent: G2/1.0
X-HTTP-UserAgent: Opera/9.64 (Windows NT 6.0; U; en) Presto/2.1.1,gzip(gfe),gzip(gfe)
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Hi,

On May 26, 12:39=A0am, Andris Pavenis <andris DOT pave DOT  DOT  DOT  AT iki DOT fi> wrote:
> On 05/26/2009 12:17 AM, Rugxulo wrote:
>
> > On May 25, 7:56 am, Andris Pavenis<andris DOT pave DOT  DOT  DOT  AT iki DOT fi> =A0wrote:
>
> >> Perhaps the best source is the documentation (archives
> >> present at specified URL even if not montioned in earlier post) or gcc=
-help
> >> mailing list if the information is not found in documentation.
>
> > Yes, I know. I tried (and tried and tried ...). What I discovered is
> > that "__attribute__((optimize(2)))" works on function prototypes
> > (only), good!, but "#pragma GCC optimize" seems to be a complete no-
> > op, does nothing (or else I did it wrong, searching didn't really help
> > for that). Same results with unofficial MinGW GCC 4.4.0, also.
>
> If there is no help from the documentation then You can ask in gcc-help
> mailing list (search archives at first:http://gcc.gnu.org/lists.html).

I did search there (well, May at least), not easy to find otherwise. I
also found an old (11-month old?) patch regarding this, didn't shed a
lot of light. I tried a bunch of variations, still nothing. And also
read some hint somewhere that some ICEs were a result of this new
feature, so maybe they did disable it (partially / fully) on some /
all targets, who knows. Anyways, it's not a big deal. Although, for
the record, I did find my app that previously ran fastest with -O3
(4.3.2) now runs fastest with 4.4.0's -O2 (12% slower with -O3), hence
some interest on my part. But I'm just lucky I benchmarked it first
instead of blindly assuming anything!

> >> When I tried to specify that sockets are not
> >> supported, I got build errors for libada. I do not have enough time
> >> for fixing that (I do not know Ada well enough either), so the help is
> >> appreciated.
>
> > I wish I could help, but I don't know Ada at all, and obviously don't
> > have the skills to participate more. =A0 :-(
>
> The message was sent to mailing list, so maybe somebody who can and want
> it will read the message. I'm afraid however that the probability of this
> happening is rather small unfortunatelly.

BTW, thanks again for building 4.4.0, I actually was quite eager for
it for no huge reason (although I had already heard about "target" and
"optimize" pragmas), even downloading the unofficial MinGW 4.4.0
(blech, MSVCRT.DLL).   ;-)

In short, being "stuck" to 4.3.2 / 4.3.3 for Ada wouldn't be the end
of the world. I mean, hey, it's Ada 83 / 95 / partial 2005, right? Not
too shabby. So thanks for what you've built so far. At least with
Gautier's 3d engine, DOS has at least one good publicly available
DJGPP Ada app! I mean, if people can still use TC++ 1.01 (and FreeDOS
does, somewhat), they can use "old" GCC 4.3.3 for many years. Worst
case scenario.   :-)