Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gccgo: syscall package differences #3071

Closed
alberts opened this issue Feb 19, 2012 · 6 comments
Closed

gccgo: syscall package differences #3071

alberts opened this issue Feb 19, 2012 · 6 comments
Milestone

Comments

@alberts
Copy link
Contributor

alberts commented Feb 19, 2012

What steps will reproduce the problem?

GC=gccgo go build .

What is the expected output?

This code compiles against the linux/amd64/6g syscall package on Linux

What do you see instead?

./main.go:12:17: error: reference to undefined identifier ‘syscall.Getcwd’
./main.go:15:17: error: reference to undefined identifier ‘syscall.Adjtimex’
./main.go:37:17: error: reference to undefined identifier ‘syscall.Getdents’
./main.go:42:14: error: reference to undefined identifier ‘syscall.Getrlimit’
./main.go:47:17: error: reference to undefined identifier ‘syscall.InotifyInit1’
./main.go:67:14: error: reference to undefined identifier ‘syscall.Setrlimit’
./main.go:73:14: error: reference to undefined identifier ‘syscall.Sysinfo’
./main.go:75:14: error: reference to undefined identifier ‘syscall.Tgkill’
./main.go:83:14: error: reference to undefined identifier ‘syscall.Ustat’
./main.go:84:14: error: reference to undefined identifier ‘syscall.Utime’
./main.go:122:14: error: reference to undefined identifier ‘syscall.SyncFileRange’
./main.go:180:14: error: reference to undefined identifier ‘syscall.Reboot’
./main.go:181:17: error: reference to undefined identifier ‘syscall.ReadDirent’
./main.go:182:20: error: reference to undefined identifier ‘syscall.ParseDirent’
./main.go:188:10: error: reference to undefined identifier ‘syscall.LsfStmt’
./main.go:189:10: error: reference to undefined identifier ‘syscall.LsfJump’
./main.go:190:10: error: reference to undefined identifier ‘syscall.LsfSocket’
./main.go:191:10: error: reference to undefined identifier ‘syscall.SetLsfPromisc’
./main.go:192:10: error: reference to undefined identifier ‘syscall.AttachLsf’
./main.go:193:10: error: reference to undefined identifier ‘syscall.DetachLsf’
./main.go:205:17: error: reference to undefined identifier ‘syscall.Time’

Lsf stuff is net package support code. Maybe gccgo uses glibc to implement those APIs?

Which compiler are you using (5g, 6g, 8g, gccgo)?

gccgo

Which operating system are you using?

linux

Which revision are you using?  (hg identify)

tip

Please provide any additional information below.

I'm working on a tool that generates a multi-package/multi-command Go project that calls
all the functions in the standard library. I'm hoping the tool will help to easily build
a big test project for the go tool. It also turned up these differences between 6g and
gccgo.

Attachments:

  1. main.go (4420 bytes)
@alberts
Copy link
Contributor Author

alberts commented Feb 19, 2012

Comment 1:

Here's the right file.

Attachments:

  1. main.go (6167 bytes)

@rsc
Copy link
Contributor

rsc commented Feb 19, 2012

Comment 2:

Labels changed: added priority-go1, removed priority-triage.

Owner changed to @ianlancetaylor.

Status changed to Accepted.

@ianlancetaylor
Copy link
Contributor

Comment 3:

Labels changed: added gccgo.

@ianlancetaylor
Copy link
Contributor

Comment 4:

Fixed on tip.
Thanks for the test case.

Status changed to Fixed.

@alberts
Copy link
Contributor Author

alberts commented Mar 1, 2012

Comment 5:

I suspect there are still some constants missing. Is the goapi checks going to catch
that?

@ianlancetaylor
Copy link
Contributor

Comment 6:

Yes, that is issue #1790.
Fixing this bug is not meant to imply that the gccgo syscall package is complete, only
that is complete enough to build your test case.

@rsc rsc added this to the Go1 milestone Apr 10, 2015
@rsc rsc removed the priority-go1 label Apr 10, 2015
@golang golang locked and limited conversation to collaborators Jun 24, 2016
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants