From mint-bounce@lists.fishpool.fi Sat Feb 14 03:26:18 2009 Message-ID: <49967915.8070508@freesbee.fr> Date: Sat, 14 Feb 2009 08:56:05 +0100 From: =?ISO-8859-1?Q?Vincent_Rivi=E8re?= User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: mint CC: Mark Duckworth Subject: Re: [MiNT] C++ Stuff References: <499665F5.809@atari-source.org> In-Reply-To: <499665F5.809@atari-source.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: vincent.riviere@freesbee.fr Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.sparemint.org id n1E8QI8U009444 Mark Duckworth wrote: > Everything is fine except when I use vectors so far. It seems if I use > vector.push_back() there is a call to an FPU function. Looks very strange. Which compiler do you use ? In my opinion, your program crashes for another reason. Possibles reasons are : - stack overflow : very common, use the "stack" program to increase it. - bug elsewhere in your program > Does anyone else think it's strange that something as simple as > vector would need FPU functions? If you compile with default options, gcc will never generate FPU instructions. Try first increasing the stack. If it doesn't change anything, write a simple program using a vector and you will see it works fine. PS : Current GCC 4.3.3 has still a bug in C++, if you try to display an int with cout it will display nothing and put cout in error state, so further cout usage will not work. -- Vincent Rivière