hardfp on lctr-b2xx (beaglebone black)

[Kristian Klausen]

Hi,

Is there a specific reason as to why the hardfp functionality is not utilized in lctr-b2xx?

I tried compiling with the flags for hardfp (like cortex-a8-hardfp), and got a 7-8% performance increase with whetstone. I don't know how well that translates to real-world usage though.

Regards,
Kristian

[Ricardo Martins]

Hi Kristian,

On Tue, Mar 22, 2016 at 11:44 PM, Kristian Klausen <kkn...@gmail.com> wrote:

Hi,

Is there a specific reason as to why the hardfp functionality is not utilized in lctr-b2xx?

For us (OceanScan-MST) lctr-b2xx is deprecated as we no longer ship systems with that configuration. We use lauv-aux and laux-aux-rpi instead.

 

I tried compiling with the flags for hardfp (like cortex-a8-hardfp), and got a 7-8% performance increase with whetstone. I don't know how well that translates to real-world usage though.

I will accept pull requests moving lctr-b2xx to hardfp as long as the live upgrade from the current softfp works.

 

Regards,
Kristian

--
You received this message because you are subscribed to the Google Groups "LSTS Toolchain" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lsts-toolchai...@googlegroups.com.
Visit this group at https://groups.google.com/group/lsts-toolchain.
To view this discussion on the web visit https://groups.google.com/d/msgid/lsts-toolchain/e00a3ee5-17f6-4294-a902-2de372245636%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Kristian Klausen]

Hi,

Thanks for the info. Am I correct when I say there is no real reason _not_ to use hardfp? I will probably just do it on ntnu-b2xx for now, and control the transition locally. (Assuming we're the only ones who have deployed that system)

Kristian

[Ricardo Martins]

On Wed, Mar 23, 2016 at 1:06 PM, Kristian Klausen <kkn...@gmail.com> wrote:

Hi,

Thanks for the info. Am I correct when I say there is no real reason _not_ to use hardfp? I will probably just do it on ntnu-b2xx for now, and control the transition locally. (Assuming we're the only ones who have deployed that system)

Right now there's no reason not to use hardfp.

 

Kristian

onsdag 23. mars 2016 11.40.57 UTC+1 skrev Ricardo Martins følgende:

Hi Kristian,

On Tue, Mar 22, 2016 at 11:44 PM, Kristian Klausen <kkn...@gmail.com> wrote:

Hi,

Is there a specific reason as to why the hardfp functionality is not utilized in lctr-b2xx?

For us (OceanScan-MST) lctr-b2xx is deprecated as we no longer ship systems with that configuration. We use lauv-aux and laux-aux-rpi instead.

 

I tried compiling with the flags for hardfp (like cortex-a8-hardfp), and got a 7-8% performance increase with whetstone. I don't know how well that translates to real-world usage though.

I will accept pull requests moving lctr-b2xx to hardfp as long as the live upgrade from the current softfp works.

 

Regards,
Kristian

--
You received this message because you are subscribed to the Google Groups "LSTS Toolchain" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lsts-toolchai...@googlegroups.com.
Visit this group at https://groups.google.com/group/lsts-toolchain.
To view this discussion on the web visit https://groups.google.com/d/msgid/lsts-toolchain/e00a3ee5-17f6-4294-a902-2de372245636%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "LSTS Toolchain" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lsts-toolchai...@googlegroups.com.
Visit this group at https://groups.google.com/group/lsts-toolchain.

To view this discussion on the web visit https://groups.google.com/d/msgid/lsts-toolchain/120242bd-cff3-4718-9375-144153cd9c90%40googlegroups.com.