Hello,
Fermat's little theorem says that ^5146 mod 5147 is 1
so similarly ^(5146+5146) mod 5147 is also 1.
Therefore it is correct that ^(5146+5147) mod 5147 is .
If you have a large exponent, you should reduce it modulo (p-1) to keep the
same result.
Regards,
Rémy.
Le dim. 11
at 11:03 AM Austin Clements
> wrote:
>
>> On Tue, Apr 16, 2019 at 1:23 AM Rémy Oudompheng
>> wrote:
>>
>>> Thanks Austin,
>>>
>>> The application workload is a kind of fragmentation torture test as it
>>> involves a mixture of many long-
the huge page flag manipulation to confirm and/or fix
> this. In $GOROOT/src/runtime/internal/sys/arch_amd64.go (or whichever GOARCH
> is appropriate), set HugePageSize to 0. Though there's a danger that Linux's
> transparent huge pages could blow up your application's resi
Hello,
In a large heap program I am working on, I noticed a peculiar change in the
way virtual memory is reserved by the runtime : with comparable heap size
(about 150GB) and virtual memory size (growing to 400-500GB probably due to
a kind of fragmentation), the number of distinct memory mappings
With this proposal, can you tell whether the following function F
returns one argument (a function) or two arguments (a function and an
error) :
func F() func(string) []byte, error {
blah
}
Rémy.
2017-07-23 18:18 GMT+02:00 Gert :
> I personally don't think () is necessary for output types and
The math/big library has basic routines implemented in assembly for
most common architectures, with all the math written in Go atop those.
Rémy.
2017-07-22 17:39 GMT+02:00 Hugh S. Myers :
> Is math/big pari based?
>
> On Sat, Jul 22, 2017 at 8:36 AM, Rémy Oudompheng
> wrote:
>>
2017-07-22 17:19 GMT+02:00 Rémy Oudompheng :
> 2017-07-22 16:48 GMT+02:00 me :
>> How does GoLang compare to other languages for mathematics dealing with
>> really large numbers?
>>
>> Prefer the ability to work with 2GB sized strings as numbers (need much
>> big
2017-07-22 16:48 GMT+02:00 me :
> How does GoLang compare to other languages for mathematics dealing with
> really large numbers?
>
> Prefer the ability to work with 2GB sized strings as numbers (need much
> bigger than int64)
>
> I see there is this:
> https://golang.org/pkg/math/big/
>
> And prob
2017-07-17 15:56 GMT+02:00 Jeff Templon :
> Coming back to this, now that my Go knowledge is increasing:
>
> On Saturday, July 8, 2017 at 5:58:59 PM UTC+2, Andy Balholm wrote:
>>
>> I noticed your “naive explanation” after I sent my message. But I think it
>> is the real explanation.
>
>
> it turns
There is no floating point number which is exactly equal to either 0.05 or
0.15 so in your examples the simple "round to nearest" rule apply (no tie
implied).
Rémy.
Le 2 juil. 2017 9:15 AM, "Uli Kunitz" a écrit :
One could justify it, if the rounding rule is "rounding to nearest, ties to
even"
2017-07-02 6:20 GMT+02:00 Dan Kortschak :
> Is this expected:
>
> ```
> package main
>
> import (
> "fmt"
> "strconv"
> )
>
> func main() {
> fmt.Print(strconv.FormatFloat(0.5, 'f', 0, 64))
> }
> ```
>
> ```
> 0
> ```
>
> https://play.golang.org/p/HEyxpGPrX3
>
> This is trun
11 matches
Mail list logo
