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: Fri, 19 Jul 2002 09:16:00 -0000 [thread overview] Message-ID: <20020719161600.29635.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: Fri, 19 Jul 2002 18:54:36 +0200 Hi, the ICE is caused by the code in line 2450 and line 2463 of act.informative.c (lines 10398 and 10411 of the preprocessed file). If you replace the right hand sides of the = operator by something else, the code compiles fine. The offending code can be reduced to --------------------------snip here------------------------- typedef A = 0; --------------------------snip here------------------------- which will cause an ICE if compiled with gcc 3.1 or the main trunk as of 20020715 (checked on i686-pc-linux-gnu and mips-sgi-irix6.5). IMHO the code is illegal. Since it was accepted by earlier versons of the compiler there seems to be an accepts-illegal bug for gcc 2.95.x 3.0.x. Greetings, Volker Reichelt http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7353
next reply other threads:[~2002-07-19 16:16 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-07-19 9:16 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-08-28 8:06 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=20020719161600.29635.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: linkBe 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).