public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "speirofr at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/66903] The gcc 4.9.2 crashes when processing declarations such as: int (( ... (x) ... ))
Date: Fri, 17 Jul 2015 07:38:00 -0000 [thread overview]
Message-ID: <bug-66903-4-VgDEEItl3t@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66903-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66903
--- Comment #1 from Salva Peiró <speirofr at gmail dot com> ---
Created attachment 36001
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36001&action=edit
parens.i: Preprocesed sourced with gcc -v -save-temps
>From gcc-bugs-return-492604-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 17 08:12:54 2015
Return-Path: <gcc-bugs-return-492604-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12490 invoked by alias); 17 Jul 2015 08:12:54 -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 12438 invoked by uid 48); 17 Jul 2015 08:12:51 -0000
From: "doko at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/66904] New: cmd/go: "#cgo pkg-config:" comments do not work with gccgo
Date: Fri, 17 Jul 2015 08:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: 5.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: doko at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-66904-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-07/txt/msg01494.txt.bz2
Content-length: 532
https://gcc.gnu.org/bugzilla/show_bug.cgi?idf904
Bug ID: 66904
Summary: cmd/go: "#cgo pkg-config:" comments do not work with
gccgo
Product: gcc
Version: 5.2.1
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
Target Milestone: ---
see https://github.com/golang/go/issues/11739
next prev parent reply other threads:[~2015-07-17 7:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-17 7:34 [Bug c/66903] New: " speirofr at gmail dot com
2015-07-17 7:38 ` speirofr at gmail dot com [this message]
2015-07-17 9:01 ` [Bug c/66903] " speirofr at gmail dot com
2015-07-19 3:36 ` pinskia at gcc dot gnu.org
2015-07-19 9:16 ` speirofr at gmail dot com
2015-07-21 11:08 ` mpolacek at gcc dot gnu.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-66903-4-VgDEEItl3t@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).