Dear all,
> @fixeria: re the C compiler used on the FreeBSD build slave:
> it is actually, apparently:
>
> FreeBSD clang version 3.4.1
> 20140512
> x86_64-unknown-freebsd10.3
>
> At least that's what a libosmocore ./configure step shows in
> its config.log.
I would like to start a little discussion about FreeBSD build
slave. As it turned out, every new commit is being checked on
clang compiler too! It was a bit unexpectedly to me, because
we already discussed about this in Gerrit:
https://gerrit.osmocom.org/#/c/2100/
> Max:
> > Do we officially support anything besides gcc?
>
> Harald:
> > not really, but then it is also nice to be portable. My vote
> > would be to merge the current patch under discussion, but open
> > a ticket as a reminder that this should be made more portable.
> > I suppose mplayer/ffmpeg/fftw or other libs with heavily
> > optimized algorithms also have a solution to that.
Recently I decided to dig into FreeBSD's world, because one of my
changes in Gerrit does build fine on Debian slave, but doesn't on
FreeBSD. So, I spent a whole night with my laptop and finally
installed and configured FreeBSD first time in my experience.
https://gerrit.osmocom.org/#/c/2100/
I am running 11.0 STABLE, and by default it comes with clang as
default compiler. There is no GCC installed by default. I tried
to build my change with different versions of clang and found the
following interesting facts:
- Recent clang-4.0 does support the __builtin_cpu_supports call,
so runtime CPU detection should work in this case too. I don't
know if it works in other versions. So, I suggest to add a new
configure.ac task, which would check whether compiler supports
this call or not.
- Regarding to my change, it builds fine on several tested clang
versions: clang-3.4.2, clang-3.9, clang-4.0. And I see two
possible reasons, why the build fails on FreeBSD:
1) Version 3.4.1 is pretty dated, and we cat try to upgrade it.
2) Clang compiles the source code in a different way, when some
SIMD flags are provided. But target CPU doesn't support some
of provided SIMD flags. Now in both OsmoTRX and libosmocore
we only check whether compiler supports some SIMD flags, but
we don't check whether these flags are supported by current
build machine CPU. So, lack of the last check and specific
optimization / compilation way of clang may cause the fail.
I still need to know supported SIMD features of FreeBSD
build machine to confirm or refute this assumption.
I also have an idea: what if we could build our projects with several
compilers (GCC and clang) and with their several versions (the three
latest for example) on Jenkins at the same time? I think, it would be
great to keep our projects as portable as possible.
With best regards,
Vadim Yanitskiy.
On Fri, May 05, 2017 at 03:28:48PM +0000, postmaster(a)Radisyscorp.onmicrosoft.com wrote:
> Your message to Sivasankari.Theerthagiri(a)radisys.com couldn't be delivered.
>
> Sivasankari.Theerthagiri wasn't found at radisys.com.
Dear Radisys,
since we are having a problem with a patch from Sivasankari Theerthagiri and
since that contact is apparently no longer available, do you have another
contact that could help resolve the issue?
Thanks!
~N
> From: Neels Hofmeyr <nhofmeyr(a)sysmocom.de>
> To: openbsc(a)lists.osmocom.org
> CC: sivasankari <Sivasankari.Theerthagiri(a)radisys.com>
> Subject: PCU broken: PACCH paging omitted
> User-Agent: Mutt/1.5.23 (2014-03-12)
>
> Trying to fix a PCU breakage, I introduced another error, causing paging to be
> broken. All the details are at:
> https://osmocom.org/issues/2241
> https://gerrit.osmocom.org/2420
>
> I need help: could anyone verify whether the patch is doing the right thing
> now? Otherwise we will need to revert the whole series of breaking patches:
>
> http://git.osmocom.org/osmo-pcu/commit/?id=da7250ad2c1cd5ddc7d3c6e10435a00b…
> "Add counter at BTS level And statistics at TBF/MS level."
> sivasankari <Sivasankari.Theerthagiri(a)radisys.com>
>
> http://git.osmocom.org/osmo-pcu/commit/?id=b78a4a6dfef217c538d45949a6ae725e…
> "fix segfault: check for NULL tbf in sched_select_ctrl_msg()"
> Neels Hofmeyr <nhofmeyr(a)sysmocom.de>
>
> Thanks for any help!
>
> ~N
--
- Neels Hofmeyr <nhofmeyr(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschäftsführer / Managing Directors: Harald Welte
Hi Alexander and all,
> I don't think those patches will change this if your seeing a failure with
> a --without-sse build.
I hope, it should, because even with --without-sse we still had
-march=native.
http://git.osmocom.org/osmo-trx/commit/?id=78b5627fa1c911713a776e4aa1cb2d8f…
Neels, do you still have the same problem with running on osmo-gsm-tester
setup?
With best regards,
Vadim Yanitskiy.
Trying to fix a PCU breakage, I introduced another error, causing paging to be
broken. All the details are at:
https://osmocom.org/issues/2241https://gerrit.osmocom.org/2420
I need help: could anyone verify whether the patch is doing the right thing
now? Otherwise we will need to revert the whole series of breaking patches:
http://git.osmocom.org/osmo-pcu/commit/?id=da7250ad2c1cd5ddc7d3c6e10435a00b…
"Add counter at BTS level And statistics at TBF/MS level."
sivasankari <Sivasankari.Theerthagiri(a)radisys.com>
http://git.osmocom.org/osmo-pcu/commit/?id=b78a4a6dfef217c538d45949a6ae725e…
"fix segfault: check for NULL tbf in sched_select_ctrl_msg()"
Neels Hofmeyr <nhofmeyr(a)sysmocom.de>
Thanks for any help!
~N
--
- Neels Hofmeyr <nhofmeyr(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschäftsführer / Managing Directors: Harald Welte
Hello,
And, what is the different of "nano3G" and the "sysmocell 5000" !?
Chears,
De : "openbsc-request(a)lists.osmocom.org" <openbsc-request(a)lists.osmocom.org>
À : openbsc(a)lists.osmocom.org
Envoyé le : Jeudi 4 mai 2017 18h32
Objet : OpenBSC Digest, Vol 31, Issue 6
Send OpenBSC mailing list submissions to
openbsc(a)lists.osmocom.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.osmocom.org/mailman/listinfo/openbsc
or, via email, send a message with subject or body 'help' to
openbsc-request(a)lists.osmocom.org
You can reach the person managing the list at
openbsc-owner(a)lists.osmocom.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of OpenBSC digest..."
Today's Topics:
1. Re: osmo-bts-trx error / osmo-trx illegal instruction (core
dumped) (Max)
2. 3G openBSC (dga-mi.imi.fct(a)intradef.gouv.fr)
3. Re: 3G openBSC (Harald Welte)
4. RE: 3G openBSC (dga-mi.imi.fct(a)intradef.gouv.fr)
5. Re: dependency artifacts for faster
builds/gerrit-verifications (Neels Hofmeyr)
6. gerrit: thanks for login link (Neels Hofmeyr)
7. Re: gerrit: thanks for login link (Holger Freyther)
8. Re: dependency artifacts for faster
builds/gerrit-verifications (Neels Hofmeyr)
----------------------------------------------------------------------
Message: 1
Date: Wed, 3 May 2017 13:48:57 +0200
From: Max <msuraev(a)sysmocom.de>
To: openbsc(a)lists.osmocom.org
Subject: Re: osmo-bts-trx error / osmo-trx illegal instruction (core
dumped)
Message-ID: <6b2ef79f-5121-aea9-4c00-90adc5bb4cc2(a)sysmocom.de>
Content-Type: text/plain; charset=utf-8
You might want to have a look at 78b5627fa1c911713a776e4aa1cb2d8f3a04bd8f in osmo-trx
which seems to be related.
On 03.05.2017 13:45, Vadim Yanitskiy wrote:
> Hi Alexander and all,
>
> > I don't think those patches will change this if your seeing a failure with
> > a --without-sse build.
>
> I hope, it should, because even with --without-sse we still had -march=native.
> http://git.osmocom.org/osmo-trx/commit/?id=78b5627fa1c911713a776e4aa1cb2d8f…
--
Max Suraev <msuraev(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte
------------------------------
Message: 2
Date: Thu, 4 May 2017 09:40:14 +0000
From: "dga-mi.imi.fct(a)intradef.gouv.fr"
<dga-mi.imi.fct(a)intradef.gouv.fr>
To: "'openbsc(a)lists.osmocom.org'" <openbsc(a)lists.osmocom.org>
Subject: 3G openBSC
Message-ID:
<2BB505A96EF4274B86685F94F1A1B6FD23007140(a)INF31BRUZ--WM15.DR-RES.INTRADEF.GOUV.FR>
Content-Type: text/plain; charset="us-ascii"
Hello,
I would like to know whether the 3G openBSC platform is enough stable to start using it for data and voice services.
Which 3G femtocell do you recommand ?
Is it possible to use Sysmocom SIM for 3G UE registration?
Best regards,
Remi
[ENVOYE PAR INTERNET]
BTW, the "Sign in with Osmocom" link on the gerrit login page is really nice!
It even works as a bookmark.
Many Thanks!! (@holger?)
~N
2
1
3G openBSC
by dga-mi.imi.fct@intradef.gouv.fr
04 May '17
04 May '17
Hello,
I would like to know whether the 3G openBSC platform is enough stable to start using it for data and voice services.
Which 3G femtocell do you recommand ?
Is it possible to use Sysmocom SIM for 3G UE registration?
Best regards,
Remi
[ENVOYE PAR INTERNET]