Re: "BFD_ASSERT (out_attr[Tag_ABI_HardFP_use].i == 0) " assert

2011-04-28 Thread Barry Song
After checking much, I find the problem is caused by "-nostdlib" given to g++, if we set this option to g++ for linking, it will change the out_attr[Tag_FP_arch] to 0, which is generically be 4 for linaro new toolchain. A right process without -nostdlib doesn't cause ASSERT: #arm-none-linux-gnue

Re: "BFD_ASSERT (out_attr[Tag_ABI_HardFP_use].i == 0) " assert

2011-04-28 Thread Andrew Stubbs
On 28/04/11 02:30, Barry Song wrote: I am using the newest binary utils(2.21) and encounted the following ASSERT in arm_elf32.c: + if (out_attr[i].i == 0) + { + BFD_ASSERT (out_attr[Tag_ABI_HardFP_use].i == 0); [...] But not sure whether it is a bug.

Re: "BFD_ASSERT (out_attr[Tag_ABI_HardFP_use].i == 0) " assert

2011-04-28 Thread Barry Song
2011/4/28 Andrew Stubbs : > On 28/04/11 02:30, Barry Song wrote: >> >> I am using the newest binary utils(2.21) and encounted the following >> ASSERT in >> arm_elf32.c: >> +             if (out_attr[i].i == 0) >> +               { >> +                 BFD_ASSERT (out_attr[Tag_ABI_HardFP_use].i == 0

Re: "BFD_ASSERT (out_attr[Tag_ABI_HardFP_use].i == 0) " assert

2011-04-28 Thread Andrew Stubbs
On 28/04/11 09:59, Barry Song wrote: my other two mails explain what happened, in fact link input file is simple: There must be more than one input file to the link, otherwise I believe you wouldn't see this problem. We need to find out what the other ones are. ASSERT found just because we

Re: "BFD_ASSERT (out_attr[Tag_ABI_HardFP_use].i == 0) " assert

2011-04-28 Thread Chung-Lin Tang
I think I've seen this assert fail myself before, a long time ago... While this is probably a BFD bug of some sort, do you happen to have assembly code source files among the .o objects? Could you try adding ".eabi_attribute 27, 3" to the asm files and see if it links? On 2011/4/28 06:06 PM, Bar

Re: [alsa-devel] [PATCH] ASoC: prevent compilers from optimising pll calculation into __aeabi__uldivmod

2011-04-28 Thread Mark Brown
On Thu, Apr 28, 2011 at 10:30:24AM +1200, Michael Hope wrote: Don't top post! > Hi Mark. The fault exists in FSF GCC 4.5.2 and Linaro GCC > 4.5-2011.04. The fault does not exist in FSF GCC 4.6.0 or Linaro GCC > 4.6-2011.04. Given that nobody's reported it previously and there's already a new G

Re: "BFD_ASSERT (out_attr[Tag_ABI_HardFP_use].i == 0) " assert

2011-04-28 Thread Loïc Minier
Hey I've let this one through, but in the future would you please gzip your attachments so that they are smaller than 100 KiB total, or host them somewhere? Thanks! -- Loïc Minier ___ linaro-toolchain mailing list linaro-toolchain@lists

Re: __aeabi_uldivmod undefined for sound/soc/codecs/snd-soc-wm8974.ko, snd-soc-wm8940.ko and snd-soc-wm8510.ko

2011-04-28 Thread Chung-Lin Tang
On 2011/4/27 07:10 PM, Andrew Stubbs wrote: > On 27/04/11 10:57, Michael Hope wrote: >> Hi Andrew. I uploaded the wrong preprocessed source to the GCC >> bugzilla entry. It included the __attribute__((noinline)) workaround >> which hides the problem. > > OK, I've now reproduced the problem and r

Re: "BFD_ASSERT (out_attr[Tag_ABI_HardFP_use].i == 0) " assert

2011-04-28 Thread Barry Song
Hi Loïc, 2011/4/28 Loïc Minier : >        Hey > >  I've let this one through, but in the future would you please gzip your thanks for your help. >  attachments so that they are smaller than 100 KiB total, or host them >  somewhere? of course ok. > >    Thanks! > -- > Loïc Minier -barry __

Re: "BFD_ASSERT (out_attr[Tag_ABI_HardFP_use].i == 0) " assert

2011-04-28 Thread Barry Song
2011/4/28 Chung-Lin Tang : > I think I've seen this assert fail myself before, a long time ago... > > While this is probably a BFD bug of some sort, do you happen to have > assembly code source files among the .o objects? Could you try adding > ".eabi_attribute 27, 3" to the asm files and see if it

Toolchain summit blueprints

2011-04-28 Thread Michael Hope
Hi there. The toolchain session blueprints for the summit are now up on Launchpad: https://blueprints.launchpad.net/linaro-toolchain?searchtext=toolchain-o You can check out the schedule here: http://summit.ubuntu.com/uds-o/track/linaro-toolchain/ although it's really only for show at the mome