From: Enrico Zini <enrico@enricozini.org>
To: gcc-help@gcc.gnu.org
Cc: doko@debian.org
Subject: Strange #pragma interface behaviour introduced in gcc 4
Date: Sat, 09 Jul 2005 15:51:00 -0000 [thread overview]
Message-ID: <20050709155054.GA17365@viaza> (raw)
[-- Attachment #1: Type: text/plain, Size: 870 bytes --]
Hello,
I work with libraries with lots of templates and, to reduce compilation
time, I split long definitions in separate files, and I do explicit
template instantiations in an extra compilation unit.
This used to work fine until (and including) gcc 3.4, but broke in gcc
4. You can find a small example code at:
http://www.enricozini.org/store/testcase.tar.gz
In that example, if I remove the #pragmas, it works. With the pragmas,
it complains about the default constructor, destructor, copy constructor
and copy operation are used but not defined.
I didn't find this behaviour documented in the gcc changes files, and
I can't understand if it's a problem in my code or a problem in gcc.
I'm this writing for help.
Please keep me Cc-ed as I'm not subscribed to the list.
Ciao,
Enrico
--
GPG key: 1024D/797EBFAB 2000-12-05 Enrico Zini <enrico@debian.org>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2005-07-09 15:51 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=20050709155054.GA17365@viaza \
--to=enrico@enricozini.org \
--cc=doko@debian.org \
--cc=gcc-help@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).