X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f X-Recipient: djgpp AT delorie DOT com Message-ID: <4A1B8079.5030508@iki.fi> Date: Tue, 26 May 2009 08:39:05 +0300 From: Andris Pavenis User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b5pre) Gecko/20090510 Lightning/1.0pre Shredder/3.0b3pre MIME-Version: 1.0 To: djgpp AT delorie DOT com Subject: Re: GCC-4.4.0 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> In-Reply-To: <8ca6290b-d271-480c-8ef3-103d20aabf1e@t21g2000yqi.googlegroups.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Reply-To: djgpp AT delorie DOT com On 05/26/2009 12:17 AM, Rugxulo wrote: > Hi, > > On May 25, 7:56 am, Andris Pavenis wrote: > >> On 05/25/2009 03:41 PM, Rugxulo wrote:> Hi, >> >> >>> Thanks! (Now to figure out and test the "optimize" and "target" >>> #pragmas.) >>> >> Never used those. >> > They're new. :-) > > >> 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 myself usually avoid using constructions specific to GCC only even if I do not use different compilers. The exception is '__attribute__((format(...' which allows to have printf or scanf style argument list cheking. >> 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. :-( > 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. Andris