public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: giovannibajo@libero.it To: RaoulGough@yahoo.co.uk, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, giovannibajo@libero.it, nobody@gcc.gnu.org Subject: Re: c++/6771: [3.4 regression] [cygwin] ICE in in rest_of_compilation, at toplev.c:3761 for code with dllimport/dllexport Date: Thu, 01 May 2003 16:52:00 -0000 [thread overview] Message-ID: <20030501165210.23130.qmail@sources.redhat.com> (raw) Old Synopsis: no code emitted for locally unused class with dllexport attribute New Synopsis: [3.4 regression] [cygwin] ICE in in rest_of_compilation, at toplev.c:3761 for code with dllimport/dllexport State-Changed-From-To: open->analyzed State-Changed-By: bajo State-Changed-When: Thu May 1 16:52:10 2003 State-Changed-Why: As explained. The link-time regression seems gone, but there is an ice-on-legal on the mainline now. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6771
reply other threads:[~2003-05-01 16:52 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=20030501165210.23130.qmail@sources.redhat.com \ --to=giovannibajo@libero.it \ --cc=RaoulGough@yahoo.co.uk \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --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).