[gccsdk] New VFP/NEON capable GCC release?

Chris Gransden chrisg at care4free.net
Sat Aug 8 12:03:14 PDT 2015


In article <20150808135336.GX22681 at chiark.greenend.org.uk>,
   Theo Markettos <theo at markettos.org.uk> 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

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

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

> When we're ready, I'll try and make Jenkins generate the release file so we
> have it properly scripted, which might take a little while (the current
> server has HDD which makes builds slower than I might like).

I normally do,

./build-world
make ronative
./create-gcckit
./create-gcckit -pkg
./create-riscpkg

For some reason I always need to edit 'create-riscpkg' to get it to work.

I don't think there is anything extra you need to do for just vfp. Maybe
for neon although shared linked programs still run even though the neon
libs aren't in !SharedLibs.

Building statically and shared natively seems to be work for both neon and
vfp without any changes to the packaging.

Also if gcc is run with an insufficient wimpslot it gives the error
'Application requires a minimum of 6000K to run.' Where as to compile
anything it needs around 15000k.


Chris.





More information about the gcc mailing list