public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "doko at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/65353] New: [5 Regression] unknown ptrSize for $GOARCH "arm64" on aarch64-linux-gnu
Date: Sun, 08 Mar 2015 18:02:00 -0000	[thread overview]
Message-ID: <bug-65353-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65353

            Bug ID: 65353
           Summary: [5 Regression] unknown ptrSize for $GOARCH "arm64" on
                    aarch64-linux-gnu
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: go
          Assignee: ian at airs dot com
          Reporter: doko at gcc dot gnu.org
                CC: cmang at google dot com

$ go tool cgo -godefs types.go
unknown ptrSize for $GOARCH "arm64"

with a separately built go tool (1.2), built using gccgo-4.9, this works as
expected.

filing this as a regression for now.

$ cat types.go 
// +build ignore

package pty

import "C"

type (
        _C_int  C.int
        _C_uint C.uint
)

$ go tool cgo -godefs types.go
// Created by cgo -godefs - DO NOT EDIT
// cgo -godefs types.go

package pty

type (
        _C_int  int32
        _C_uint uint32
)


             reply	other threads:[~2015-03-08 18:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-08 18:02 doko at gcc dot gnu.org [this message]
2015-03-08 18:42 ` [Bug go/65353] " doko at gcc dot gnu.org
2015-03-08 19:03 ` pinskia at gcc dot gnu.org
2015-03-08 20:27 ` michael.hudson at canonical dot com
2015-03-09 12:16 ` rguenth at gcc dot gnu.org
2015-03-09 14:36 ` jakub at gcc dot gnu.org
2015-03-10  0:15 ` ian at gcc dot gnu.org
2015-03-10  0:16 ` ian at airs dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-65353-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).