public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "stgraber at stgraber dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/65404] cgo tool on powerpc-linux-gnu maybe incomplete
Date: Thu, 12 Mar 2015 16:27:00 -0000 [thread overview]
Message-ID: <bug-65404-4-YuzaC4sUKL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65404-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65404
Stéphane Graber <stgraber at stgraber dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |stgraber at stgraber dot org
--- Comment #3 from Stéphane Graber <stgraber at stgraber dot org> ---
Hi,
Correct, on both my powerpc and ppc64le systems, I'm running:
(vivid-ppc64el)stgraber@kelsey01:~$ go version
go version go1.4.2 gccgo (Ubuntu 5-20150309-1ubuntu1) 5.0.0 20150310
(experimental) [trunk revision 221296] linux/ppc64le
(vivid-powerpc-sbuild)root@winton-06:~# go version
go version go1.4.2 gccgo (Ubuntu 5-20150309-1ubuntu1) 5.0.0 20150310
(experimental) [trunk revision 221296] linux/ppc
The ppc64le one works fine, the powerpc one fails.
>From gcc-bugs-return-480203-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Mar 12 16:32:23 2015
Return-Path: <gcc-bugs-return-480203-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118919 invoked by alias); 12 Mar 2015 16:32:22 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 118873 invoked by uid 48); 12 Mar 2015 16:32:19 -0000
From: "ian at airs dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/65404] cgo tool on powerpc-linux-gnu maybe incomplete
Date: Thu, 12 Mar 2015 16:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ian at airs dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-65404-4-dbu5BAcuk9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65404-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65404-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-03/txt/msg01347.txt.bz2
Content-length: 165
https://gcc.gnu.org/bugzilla/show_bug.cgi?ide404
--- Comment #4 from Ian Lance Taylor <ian at airs dot com> ---
OK, found it. Thanks. Will send patch shortly.
next prev parent reply other threads:[~2015-03-12 16:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 14:49 [Bug go/65404] New: " doko at gcc dot gnu.org
2015-03-12 16:02 ` [Bug go/65404] " ian at airs dot com
2015-03-12 16:04 ` doko at gcc dot gnu.org
2015-03-12 16:27 ` stgraber at stgraber dot org [this message]
2015-03-12 16:42 ` ian at gcc dot gnu.org
2015-03-12 16:46 ` ian at airs dot com
2015-03-13 16:53 ` stgraber at stgraber dot org
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-65404-4-YuzaC4sUKL@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).