public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: corsepiu@faw.uni-ulm.de To: gcc-gnats@gcc.gnu.org Subject: c++/6477: Segfault on conflicting types in trivial code Date: Fri, 26 Apr 2002 08:56:00 -0000 [thread overview] Message-ID: <20020426154830.32694.qmail@sources.redhat.com> (raw) >Number: 6477 >Category: c++ >Synopsis: Segfault on conflicting types in trivial code >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: ice-on-illegal-code >Submitter-Id: net >Arrival-Date: Fri Apr 26 08:56:00 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Ralf Corsepius >Release: gcc version 3.1 20020424 (prerelease) >Organization: >Environment: i686-linux, binutils-2.12.90.0.4 Configured with: ../configure --enable-threads=posix --enable-long-long --prefix=/opt/gcc31 --mandir=/opt/gcc31/share/man --infodir=/opt/gcc31/share/info --with-local-prefix=/usr/local --enable-languages=c,c++ --disable-nls --enable-shared --with-system-zlib --host=i486-suse-linux --build=i486-suse-linux >Description: # g++31 -o pr6465.o pr6465.cc pr6465.cc:2: internal error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. This is a regression against 3.0.4, which correctly diagnoses the illegal code: # g++ -o pr6465.o pr6465.cc pr6465.cc:2: conflicting types for `struct Tk_PostscriptInfo' pr6465.cc:1: previous declaration as `typedef struct Tk_PostscriptInfo_*Tk_PostscriptInfo' Note: This PR replaces PR6465, which can be closed. >How-To-Repeat: Compile this code (Also in the attachment) typedef struct Tk_PostscriptInfo_ *Tk_PostscriptInfo; typedef struct Tk_PostscriptInfo Tk_PostscriptInfo; >Fix: >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: text/plain; name="pr6465.cc" Content-Disposition: inline; filename="pr6465.cc" typedef struct Tk_PostscriptInfo_ *Tk_PostscriptInfo; typedef struct Tk_PostscriptInfo Tk_PostscriptInfo;
next reply other threads:[~2002-04-26 15:56 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-04-26 8:56 corsepiu [this message] 2002-04-28 14:05 jakub 2003-01-01 19:45 neroden
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=20020426154830.32694.qmail@sources.redhat.com \ --to=corsepiu@faw.uni-ulm.de \ --cc=gcc-gnats@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).