On Mon, 2022-04-25 at 05:39 +, 'Dan Kortschak' via golang-nuts
wrote:
>
> I suspect that this is from GitHub checking out the code on windows
> with autocrlf and so converting perfectly sensible \n to \r\n, which
> is
> then not properly handled by this
>
https://github.com/golang/go/blob/96c8c
On Sun, Apr 24, 2022 at 10:17 PM hohoho syncxxx
wrote:
>
> Hello, I compile gollvm with:
> ```
> /bin/bash -c cd /llvm-project && git checkout 96b0b9a5e && cd
> llvm/tools/gollvm && git checkout d30fc0bf && cd gofrontend && git checkout
> ae20684902 && git apply /tmp/gollvm.patch && cd ../libgo/
On Sun, Apr 24, 2022 at 10:17 PM Anshul Malik wrote:
>
> I know this might seem like little too late to ask this question but I am
> learning go and I found out that go compiler will error if there are unused
> imports present in the code.
>
> One of the reasons I found is to eliminate pulling u
On Sun, 2022-04-24 at 05:21 -0700, Tiago Katcipis wrote:
> Hi,
>
> I was playing around with Go's fuzz support on a pet project of mine
> and as the fuzzer found some offending inputs it created the corpus
> entries on the file system. I fixed the issues but then something
> interesting happened on
On Sun, Apr 24, 2022 at 10:17 PM hohoho syncxxx
wrote:
>
> Hi, I meet that error in ubuntu too. And here is my env:
> LLVM: 2c5590adfe09
>
> gollvm: f17ba8c7708356ef447525e05cd6f2770845c7d7
>
> gofrontend: e3bfc0889237a5bb8aa7ae30e1cff14f90a5f941
>
> libffi: 0f2dd369cd5edcefad29b3fca4e1d08cb34f8f
Hi,
I know this might seem like little too late to ask this question but I am
learning go and I found out that go compiler will error if there are unused
imports present in the code.
One of the reasons I found is to eliminate pulling unused code and reducing
binary size. This doesn't really lo
Hi, I meet that error in ubuntu too. And here is my env:
*LLVM: 2c5590adfe09gollvm:
f17ba8c7708356ef447525e05cd6f2770845c7d7gofrontend:
e3bfc0889237a5bb8aa7ae30e1cff14f90a5f941libffi:
0f2dd369cd5edcefad29b3fca4e1d08cb34f8f19libbacktrace:
d0f5e95a87a4d3e0a1ed6c069b5dae7cbab3ed2a*
When
Hi,
I was playing around with Go's fuzz support on a pet project of mine and as
the fuzzer found some offending inputs it created the corpus entries on the
file system. I fixed the issues but then something interesting happened on
my CI pipeline, go test was failing only on windows and it was f
Hello, I compile gollvm with:
```
*/bin/bash -c cd /llvm-project && git checkout 96b0b9a5e && cd
llvm/tools/gollvm && git checkout d30fc0bf && cd gofrontend && git checkout
ae20684902 && git apply /tmp/gollvm.patch && cd ../libgo/libffi && git
checkout 8111cd0692 && cd ../libbacktrace && git che
I found that when receiving the ret val from functions，the RFT_BOOL will
use Type::make_boolean_type() which will generate a unnamed bool type,
I would like to change this to Type::lookup_bool_type();
I just wondering if this is ok ?
The code is in gofrontend/go/runtime.cc/runtime_function_type
在
10 matches
Mail list logo
