Re: [go-nuts] Enable importing vendor packages for bootstrap tools like cmd/compile, cmd/asm, ...

or your replies. --- On Tue, Jul 15, 2025 at 6:57 PM Qingwei Li wrote: > > The advantage might be consistency among stage1, 2 and 3? One code for 3 stages. Besides, developers don't need to worry about different behaviours among stage1 and 2/3. > > But I don't know the reaso

[go-nuts] Enable importing vendor packages for bootstrap tools like cmd/compile, cmd/asm, ...

Currently, the bootstrap process of `./make.bash` generate a project in /pkg/bootstrap/src/bootstrap and then install bootstrap tools like compile, asm, link, etc. However, it does not support vendor package now, i.e. the go.mod in bootstrap project contains no vendor packages. It's just plain a

[go-nuts] Re: Maybe a Bug? The Go compiler stores a stack pointer into a global object

I notice that Go1.17.7 still allocates the array on heap by calling newobject while Go1.18 allocates the array on stack. I also notice that in the release note of Go1.18 that "The garbage collector now includes non-heap sources of garbage collector work". Does the GC in 1.18 and following versi

[go-nuts] How to collect information in each package’s source code directory when building a project

I'm trying to collect information dumped in each package's source code directory when building a project. I have tried to ask in How to collect information in each package's source code directory when building a project - Getting Help - Go Forum (golangbridge.org)

Re: [go-nuts] GoLLVM: using the result of `go build -x . ` to rebuild the program got failed

; rm -r $WORK/b001/ > ``` > > The modified part of script is using llvm-goc `-c` option to compile > `utils.go, main.go` to object files with option `-emit-llvm` added for > llvm-link's final linking of all object files. > > After I get `$WORK/b001/_go_.o`, I us

Re: [go-nuts] GoLLVM: using the result of `go build -x . ` to rebuild the program got failed

c `-c` option to compile > `utils.go, main.go` to object files with option `-emit-llvm` added for > llvm-link's final linking of all object files. > > After I get `$WORK/b001/_go_.o`, I use llvm-link to link all _go_.o to get > a whole program llvm IR. But errors occur when

Re: [go-nuts] GoLLVM: using the result of `go build -x . ` to rebuild the program got failed

quot;ninja" >> >> LLVM version is 15.0.0 >> >> gollvm version is >> >> ``` >> go version go1.18 gollvm LLVM 15.0.0git 20220823 (experimental) >> linux/amd64 >> ``` >> >> 在2022年10月28日星期五 UTC+8 00:55:03 写道： >> >>> On T

Re: [go-nuts] GoLLVM: using the result of `go build -x . ` to rebuild the program got failed

962446f5337585f526e576b335a45 /data/mygo/gollvm_workarea/install/tools/buildid -w $WORK/b001/exe/a.out # internal cp $WORK/b001/exe/a.out easyPkg rm -r $WORK/b001/ ``` 在2022年10月28日星期五 UTC+8 14:17:46 写道： > Thanks. What I meant was that you showed us the errors from the generated > sh

Re: [go-nuts] GoLLVM: using the result of `go build -x . ` to rebuild the program got failed

r supports that option. The > errors about -fgo-importcfg and -ffile-prefix-map can be ignored. > > Not sure what is happening elsewhere, though. You showed the output > but not the commands. > > Ian > > > > > On Thu, Oct 27, 2022 at 12:05 PM 'Qing

Re: [go-nuts] GoLLVM: using the result of `go build -x . ` to rebuild the program got failed

ion '-fgo-importcfg=/dev/null' > > The Go command only passes this option to the compiler if it thinks that > the compiler is the main go compiler ("gc") as opposed to gollvm. What > output do you get when you run "go version" ? > > Thanks, Tha

[go-nuts] GoLLVM: using the result of `go build -x . ` to rebuild the program got failed

the GoLLVM is based on LLVM 15.0.0 Example to reproduce: The structure of project is as follows: ``` easyPkg/ ├── go.mod ├── main.go └── Pkg └── utils.go ``` main.go ``` package main import "easyPkg/Pkg" func main() { Pkg.PkgFunc() } ``` utils.go ``` package Pkg func PkgFunc() {