Re: [Boost-bugs] [Boost C++ Libraries] #12948: Unexpected snprintf result is on Android ARM

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #12948: Unexpected snprintf result is on Android ARM
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2017-04-06 19:19:32

#12948: Unexpected snprintf result is on Android ARM
------------------------------------+----------------------
  Reporter:  Lev Sch <zorechfan@…>  |      Owner:  olli
      Type:  Bugs                   |     Status:  reopened
 Milestone:  To Be Determined       |  Component:  context
   Version:  Boost 1.64.0           |   Severity:  Problem
Resolution:                         |   Keywords:
------------------------------------+----------------------

Comment (by olli):

 Replying to [comment:38 emile.cormier.jr@…]:
 > Are these fixes going to be introduced into Boost 1.64.0, or is it now
 too late for that?

 the commit fixing the snprintf is merged to master and should be included
 in boost-1.64.0

 > We have also observed strange snprintf behavior when it is called within
 the context of a Boost coroutine. The problem goes away if we revert back
 to Boost 1.62.0.

 I was forced to change the assembler implementations to get better
 performance

 > Our platform is the Beaglebone Black, using this Debian image:
 https://debian.beagleboard.org/images/bone-debian-8.7-iot-

 armhf-2017-03-19-4gb.img.xz
 >
 > Processor: AM355x, Cortex-A8, Neon, VFPv3
 >
 > We are cross-compiling Boost and our application using Ubuntu's
 {{{g++-4.9-arm-linux-gnueabihf}}}, which is based on sources from Linaro
 GCC.
 >
 > Boost was built with:
 >
 > {{{
 > ./b2 link=static variant=release threading=multi toolset=gcc-arm \
 > cxxflags=-std=c++11 target-os=linux abi=aapcs binary-format=elf \
 > architecture=arm address-model=32
 > }}}
 >
 > We can attempt to run unit tests after Oliver and Lev sort things out.

 you could test the sources (execut teh unit-tests) of boost.context from
 branch develop
 but gcc-4.9 can not deal with the overloads of callcc() (gcc-5.x does
 compile) but test_fcontext.cpp tests the basic functionality - so good
 verify at least the fcontext-API is correct (contains a snprintf test).

 > Oliver, our company will gladly ship you an ARM board (Beaglebone Black)
 if you need one. Our project is heavily dependent on Boost.Coroutine, and
 therefore Boost.Context as well.

 I've an armv7l board (ODROID-X V1) running Ubuntu + gcc-5 -> no problems
 with boost.context

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/12948#comment:40>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.