I have found that -O3 mode does not work with mingw. I suspect linker issue....

mirek wrote on Thu, 07 April 2016 23:48

I have found that -O3 mode does not work with mingw. I suspect linker issue....

So it is not just me then?

Anyway, I might be able to circumvent the problem.

What I'm doing in the atexit method is basically leak detection. How did you manage to do leak detection in U++, since such code needs to run after global destructors, right?

That sounds BLITZ related. Sometimes, BLITZ can hide error.

Nice!

I've been trying to integrate more and more GCC in my stuff, but it is not that easy.

This is not related to U++, but me doing funky stuff on program terminate, but often with GCC I have a weird problem: the program crashes on the atexit stage, where I do a pre-global destructor cleanup. And the weird part is that this only happens on a fresh compile after a clean. I compile in optimized mode, crashes. Recompile without optimal mode, no crash. After this, no mater how many times I compile in optimized mode, no more crash and the problem goes away for hours or until I shut down everything and clean the build folder.

This happens on Windows only, and anyway I can't Valgrind, since it is in optimized mode.

But without the cleanup, GCC looks like it works well and I try to compile once a week.

inline void _free(void** p) {
	if (*p) {
		STDLIB_GC--;
		free(*p);
	}
	*p = 0;
}