From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexander Holler Date: Fri, 29 Oct 2010 17:05:14 +0200 Subject: [U-Boot] Most ARM CPU's have buggy clear_bss? In-Reply-To: <4CCAE01D.9090005@free.fr> References: <4CC93C74.6050309@ahsoftware.de> <4CC94305.8060001@ahsoftware.de> <4CCA8AF0.3000201@ahsoftware.de> <4CCA91AD.3060806@free.fr> <4CCAB659.5010309@ahsoftware.de> <4CCAB954.5050506@free.fr> <4CCABEAF.40305@ahsoftware.de> <4CCACE26.8060104@free.fr> <4CCADC10.9010205@ahsoftware.de> <4CCAE01D.9090005@free.fr> Message-ID: <4CCAE2AA.7080205@ahsoftware.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Am 29.10.2010 16:54, schrieb Albert ARIBAUD: > Le 29/10/2010 16:37, Alexander Holler a ?crit : >> Hello, >> >> I don't quote the rest, just read the mails before. ;) >> >> >> Here is the what I've done with the current head and the resulting >> output: >> ------------------------------------------------------------------------ > > The generated assembler code isn't really workable, at least I don't > feel comfortable with it. Could you instead do an objdump -d -S > .../nand.o > nand.lst and make the nand.lst files for each case available? Here it is: http://ahsoftware.de/nand.lst.notworking.gcc.4.5.1_without-fpic and http://ahsoftware.de/nand.lst.working.gcc.4.5.1_with-fpic I could offer the output of "gcc ... -gstabs+ -Wa,-ahldn -c nand.c >nand.s" too, this is what I'm often using but it looks like the output of objdump ;) Regards, Alexander