public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Raoul Gough" <raoulgough@clara.co.uk> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/6771: no code emitted for locally unused class with dllexport attribute Date: Mon, 25 Nov 2002 14:36:00 -0000 [thread overview] Message-ID: <20021119130605.32527.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/6771; it has been noted by GNATS. From: "Raoul Gough" <raoulgough@clara.co.uk> To: <gcc-gnats@gcc.gnu.org>, <gcc-prs@gcc.gnu.org>, <RaoulGough@yahoo.co.uk> Cc: Subject: Re: c++/6771: no code emitted for locally unused class with dllexport attribute Date: Tue, 19 Nov 2002 13:05:19 -0000 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database =gcc&pr=6771 This bug was already fixed in the mingw/cygwin branch. Building with, for example, cygwin-mingw-gcc-3_2-branch (or 3_1 AFAIK) makes the problem disappear. I guess the bug should be moved to the "closed" state or equivalent. Regards, Raoul Gough.
next reply other threads:[~2002-11-19 13:06 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-11-25 14:36 Raoul Gough [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-01 16:56 Giovanni Bajo 2002-05-24 5:46 Raoul Gough 2002-05-22 10:16 RaoulGough
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=20021119130605.32527.qmail@sources.redhat.com \ --to=raoulgough@clara.co.uk \ --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).