------- Comment #31 from rogerio at rilhas dot com 2010-08-12 18:32 ------- (In reply to comment #28) > I built your test case with gcc and g++ without optimizations, and it worked > fine.
Just like my script? I noticed that I'm using a not-the-newest GCC version, and I know that some older version 3.xxx didn't have the problem (a few years ago). Maybe it is something changed in the most recent versions? > I could only get it to fail with gcc/g++ by optimizing, but then, I > could get it to fail with MSVC by optimizing. Seems to me, gcc and MSVC are > doing the same thing, or you have some modified version of gcc that is not > acting the same way as the official version. I'm sorry, but I'm new to Linux, I'm not sure if the GCC I'm using got "tweaked" in any way. It came with Ubuntu, but I don't know if it got upgraded with Code::Blocks. I thought that "-save-temps" would provide you with that information, didn't it? How can I get such information? > Also, please provide an official spec for this "cdecl" you keep referring to. Sorry, I did send you one in my variable arguments report and I forgot to send it here olso. http://sco.com./developers/devspecs/abi386-4.pdf, see "Figure 3-48: C Stack Frame". It is not a standard, as I'm sure you know, but it is a well-defined concept. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45265
