Thanks much, to you and Jan Merci.
I needed it to validate whether the performance gap in my library was due
to bounds checking or not. If it was, then I would try harder to use tips
to reduce bounds checking. I wasn't planning on running it in production.
I ended up having to use
On Sun, Jun 16, 2019, 13:53 Ugorji Nwoke wrote:
> I know this is an old thread, but is -B still supported?
>
That compiler flag provides compiling a program, semantic of which isn't
compatible with the Go language specification.
It's only valid use is to enable easy evaluation of the bounds
It has been, yes, and unless it changed in the last few weeks, it still is.
I use to to measure cost as an awareness metric, but seldom run that way.
Go is safe until you do that, then it becomes unsafe. Too risky for serious
use.
On Sun, Jun 16, 2019 at 4:53 AM Ugorji Nwoke wrote:
> I know
I know this is an old thread, but is -B still supported?
On Monday, August 27, 2012 at 2:09:19 AM UTC-4, minux wrote:
>
>
> On Monday, August 27, 2012, bluehorn wrote:
>>
>> Is "-gcflags -B" still supported in go1.0.2? I suppose it was gone
>> already.
>>
> It is still there.
>
--
You
