public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Giovanni Bajo" <giovannibajo@libero.it>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/8378: [Windows] G++ crashes (in certain cirumstances) when returning statics
Date: Wed, 02 Apr 2003 02:56:00 -0000	[thread overview]
Message-ID: <20030402025600.13607.qmail@sources.redhat.com> (raw)

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

From: "Giovanni Bajo" <giovannibajo@libero.it>
To: <gcc-gnats@gcc.gnu.org>,
	<msinilo@kki.net.pl>,
	<gcc-bugs@gcc.gnu.org>,
	<nobody@gcc.gnu.org>,
	<gcc-prs@gcc.gnu.org>
Cc: "Wolfgang Bangerth" <bangerth@ices.utexas.edu>
Subject: Re: c++/8378: [Windows] G++ crashes (in certain cirumstances) when returning statics
Date: Wed, 2 Apr 2003 04:50:00 +0200

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&p
 r=8378
 
 Confirmed with cygwin 3.2. Redux:
 
 -----------------------------------------
 struct __attribute__((dllimport)) Foo
 {
  static int static_func();
 };
 
 int bar = Foo::static_func();
 
 int Foo::static_func()
 {
  return 0;
 }
 -----------------------------------------
 $ g++ -c pr8378.cpp
 pr8378.cpp: In static member function `static int Foo::static_func()':
 pr8378.cpp:12: Internal compiler error in rest_of_compilation, at
 toplev.c:3491
 Please submit a full bug report,
 with preprocessed source if appropriate.
 See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
 
 Notice this is a regression from 2.95:
 
 $ g++-2 -c pr8378.cpp
 pr8378.cpp: In function `static int Foo::static_func()':
 pr8378.cpp:10: warning: inconsistent dll linkage for `static int
 Foo::static_fun
 c()'. dllexport assumed.
 
 If the definiiton of the variable "bar" is moved after the definition of the
 static function, the ICE disappears and GCC 3.2 emits a warning message just
 like 2.95.
 Synopsis can now be changed to something more appropriate, and class too
 (it's ice-on-legal-code).
 
 Giovanni Bajo
 


                 reply	other threads:[~2003-04-02  2:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030402025600.13607.qmail@sources.redhat.com \
    --to=giovannibajo@libero.it \
    --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).