public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Volker Reichelt <reichelt@igpm.rwth-aachen.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/8772: Segmentation fault on 3 lines of template code
Date: Fri, 17 Jan 2003 14:56:00 -0000	[thread overview]
Message-ID: <20030117145605.30535.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/8772; it has been noted by GNATS.

From: Volker Reichelt <reichelt@igpm.rwth-aachen.de>
To: gcc-gnats@gcc.gnu.org, sneechy@hotmail.com, gcc-bugs@gcc.gnu.org,
        gdr@integrable-solutions.net, bangerth@ticam.utexas.edu
Cc:  
Subject: Re: c++/8772: Segmentation fault on 3 lines of template code
Date: Fri, 17 Jan 2003 16:48:56 +0100

 The ICE is fixed with the new parser.
 I now get:
 
 PR8772.cc:7: error: type/value mismatch at argument 1 in template parameter 
    list for `template<template<int <anonymous> > class F> struct C'
 PR8772.cc:7: error:   expected a type, got `A<<anonymous> >::B'
 
 (Testcase in preparation.)
 
 
 What are we going to do with the PR w.r.t. the how-to-make-to-code-legal issue?
 Leave it open, close it, suspend it, open a new PR?
 Any suggestions, Gaby, Wolfgang?
 
 Regards,
 Volker
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8772
 
 


             reply	other threads:[~2003-01-17 14:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-17 14:56 Volker Reichelt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-20  9:46 Volker Reichelt
2003-01-18  9:36 Gabriel Dos Reis
2003-01-17 15:56 Wolfgang Bangerth
2002-12-03  8:16 Gabriel Dos Reis
2002-12-03  8:06 Wolfgang Bangerth
2002-12-02 14:56 Gabriel Dos Reis
2002-12-02 12:45 bangerth
2002-12-01  1:46 Paolo Carlini

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=20030117145605.30535.qmail@sources.redhat.com \
    --to=reichelt@igpm.rwth-aachen.de \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).