public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Reichelt <reichelt@igpm.rwth-aachen.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/7353: Compiler dies on known working code (as of gcc 3.0)
Date: Wed, 28 Aug 2002 08:06:00 -0000	[thread overview]
Message-ID: <20020828145605.25716.qmail@sources.redhat.com> (raw)

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

From: Reichelt <reichelt@igpm.rwth-aachen.de>
To: gcc-gnats@gcc.gnu.org, mike@velgarian.sytes.net, gcc-bugs@gcc.gnu.org,
        nobody@gcc.gnu.org
Cc:  
Subject: Re: c/7353: Compiler dies on known working code (as of gcc 3.0)
Date: Wed, 28 Aug 2002 17:33:55 +0200

 Hi again,
 
 sorry, I wasn't aware that "typedef A = 0;" is a valid gcc extension.
 So, your code was in fact valid (although only for gcc) and the bug is an
 ice-on-legal-code for 3.1.x, 3.2 and the main trunk (3.3 20020816).
 Because it's a regression, it should be marked high priority.
 
 BTW, for the code "typedef A = 0;" the error message is
 
 bug.c:1: Internal compiler error in make_decl_rtl, at varasm.c:839
 Please submit a full bug report, [etc.]
 
 For "void foo () { typedef A = 0; }" I get
 
 bug.c:1: Internal compiler error in gen_typedef_die, at dwarf2out.c:11035
 Please submit a full bug report, [etc.]
 
 instead (if I compile the code with "-g" enabled).
 
 Greetings,
 Volker Reichelt
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7353
 
 


             reply	other threads:[~2002-08-28 14:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-28  8:06 Reichelt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-09 14:53 zack
2002-10-07 23:13 zack
2002-07-19  9:16 Reichelt
2002-07-18 14:26 mike

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=20020828145605.25716.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).