I have a fairly complex build with lots of makefiles. One C++ file is
auto-generated and included into this build into many applications which
uses it. Basicly I need to compile it with -O0 when all other files are
compiled with -O2.

In Microsoft C++ compiler it's quite easy to turn off the optimization for
this particular file with a #pragma:

#ifdef _MSC_VER
#pragma optimize("", off)
#endif

void FuncA()
{

..
}

#ifdef _MSC_VER
#pragma optimize("", on)
#endif

Is there a similar thing you can do with gcc/g++?

Thanks in advance.
-- John

[ Post a follow-up to this message ]

On 2005-01-27, John Smith <john.smith@x-formation.com> wrote:
> I have a fairly complex build with lots of makefiles. One C++ file is
> auto-generated and included into this build into many applications which
> uses it. Basicly I need to compile it with -O0 when all other files are
> compiled with -O2.
>
> In Microsoft C++ compiler it's quite easy to turn off the optimization for
> this particular file with a #pragma:
>
> #ifdef _MSC_VER
> #pragma optimize("", off)
> #endif
>
> void FuncA()
> {
>
> ..
> }
>
> #ifdef _MSC_VER
> #pragma optimize("", on)
> #endif
>
> Is there a similar thing you can do with gcc/g++?

Have you considered manipulating make files and not the source file?
After all make if fairly flexible to implement things like that (check
for example target specific variables).

--
Minds, like parachutes, function best when open

[ Post a follow-up to this message ]

> Have you considered manipulating make files and not the source file?
> After all make if fairly flexible to implement things like that (check
> for example target specific variables).

Yes I have considered it and know it's the only way out, if nothing better
comes up. I already know about target specific variables.

However my build is special. The *.cpp file in mind is included through
another cpp file like this:

#include "foo.cpp"

So if I disable optimization it affects a lot more then just the code I
want.
The only way to solve this is to restructure the build process to become
more "standard". However theres many good reasons for the way it's done with
including code into other files and restructuring it, will only cause new
problems.

-- John

[ Post a follow-up to this message ]