public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "daniel.kruegler at googlemail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/60767] [ICE] use of "using" inside template causes failure in retreive_specialization
Date: Sat, 05 Apr 2014 14:54:00 -0000	[thread overview]
Message-ID: <bug-60767-4-v3elQXq9ud@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60767-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60767

Daniel Krügler <daniel.kruegler at googlemail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |daniel.kruegler@googlemail.
                   |                            |com

--- Comment #1 from Daniel Krügler <daniel.kruegler at googlemail dot com> ---
The code fails also for gcc 4.9.0 trunk
>From gcc-bugs-return-448372-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Apr 05 15:03:16 2014
Return-Path: <gcc-bugs-return-448372-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13583 invoked by alias); 5 Apr 2014 15:03:15 -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 13558 invoked by uid 48); 5 Apr 2014 15:03:10 -0000
From: "w6ws at earthlink dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/60751] Extra comma in WRITE statement not diagnosed
Date: Sat, 05 Apr 2014 15:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: w6ws at earthlink dot net
X-Bugzilla-Status: WAITING
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-60751-4-x3uFd9wQDE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-60751-4@http.gcc.gnu.org/bugzilla/>
References: <bug-60751-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: 2014-04/txt/msg00392.txt.bz2
Content-length: 567

http://gcc.gnu.org/bugzilla/show_bug.cgi?id`751

--- Comment #5 from Walter Spector <w6ws at earthlink dot net> ---
> It seems quite trivial to fix, but does it really worth the work?

Well, we had an instance where this accidentally slipped into our code.  Later
on, our nightly regression runs crashed with several non-gfortran (and
non-Intel) compilers.

The extension itself is pretty gratuitous.  It adds nothing to the language,
yet can quietly promote incompatibilities.  Since g95 also accepts it, I am
assuming it came into the compiler before the split.


  reply	other threads:[~2014-04-05 14:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-05  0:30 [Bug c++/60767] New: [ICE] [c++11] [4.8.2] " zreed1 at gmail dot com
2014-04-05 14:54 ` daniel.kruegler at googlemail dot com [this message]
2014-12-14 14:26 ` [Bug c++/60767] " ville.voutilainen at gmail dot com
2014-12-18 12:18 ` ktietz 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-60767-4-v3elQXq9ud@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).