public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/34178] [4.1/4.2/4.3 Regression] Compilation using -frepo fails Date: Tue, 27 Nov 2007 17:24:00 -0000 [thread overview] Message-ID: <20071127172419.17889.qmail@sourceware.org> (raw) In-Reply-To: <bug-34178-15404@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from jakub at gcc dot gnu dot org 2007-11-27 17:24 ------- The problem is that repo_emit_p decides something needs to be emitted as if -fno-repo was used, but import_export_decl then can just ignore it and not emit it anyway (set import_p = true). When repo_emit_p said it should be emitted, it doesn't add it to pending_repo, and then import_export_decl because -frepo implies -fno-implicit-templates. So, IMHO either we replace the occurences of flag_implicit_templates in import_export_decl with flag_implicit_templates && !flag_use_repository, i.e. when -frepo, we just honor what repo_emit_p told us, don't try to override it, or at the end of function if (flag_use_repository && import_p && emit_p == 2) call some new function in repo.c which will add it to pending_repo. -- jakub at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mmitchel at gcc dot gnu dot | |org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34178
next prev parent reply other threads:[~2007-11-27 17:24 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-11-21 20:15 [Bug c++/34178] New: " rbuergel at web dot de 2007-11-25 3:02 ` [Bug c++/34178] [4.1/4.2/4.3 Regression] " pinskia at gcc dot gnu dot org 2007-11-27 17:24 ` jakub at gcc dot gnu dot org [this message] 2007-11-27 18:44 ` jakub at gcc dot gnu dot org 2007-11-27 22:06 ` mmitchel at gcc dot gnu dot org 2007-11-28 6:41 ` jakub at gcc dot gnu dot org 2007-12-09 21:27 ` jakub at gcc dot gnu dot org 2007-12-09 21:32 ` jakub at gcc dot gnu dot org
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=20071127172419.17889.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).