[gccsdk] New VFP/NEON capable GCC release?

Lee Noar leenoar at sky.com
Sun Aug 9 05:03:51 PDT 2015

On 08/08/15 14:53, Theo Markettos wrote:
> On Wed, Aug 05, 2015 at 08:48:37PM +0100, Lee Noar wrote:
>> Obviously, it will be necessary to package the VFP versions of the
>> runtime libraries. The shared libraries should be stored in
>> !SharedLibs.lib.abi-2/0.vfp. Binaries needs to be linked with
>> -mfpu=vfp so that the dynamic linker knows to look for VFP libraries.
>> I can't remember if I documented that; I'll have to check.
> So, what do I need to do a release:
> svn co ...
> cd gcc4
> <bump version number in riscpkg-versions, setup-gcc-params>
> ./build-world
> ./create-gcckit -pkg
> ./create-riscpkg

As Chris says, you'll have to do make ronative after build-world.

> Anything else?  I don't need to do anything to the compiler build to enable
> VFP?  It's purely a runtime flag for GCC?

That's right, the VFP libraries are built by default. By specifying
-mfpu=vfp to compiler and linker, GCC will generate VFP instructions,
and select the correct runtime libraries.

> Lee or Chris, would you mind adding the VFP libraries to create-riscpkg,
> since you know what's necessary and I dont?

Yes, I should be able to do that; shall I assume that for simplicity,
the VFP libraries are to be bundled with the normal ones?


More information about the gcc mailing list