public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "iains at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/42843] --enable-build-with-cxx plugin tests fail
Date: Sat, 17 Jul 2010 07:20:00 -0000 [thread overview]
Message-ID: <20100717072032.29182.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42843-5394@http.gcc.gnu.org/bugzilla/>
------- Comment #22 from iains at gcc dot gnu dot org 2010-07-17 07:20 -------
(In reply to comment #16)
> Created an attachment (id=21188)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21188&action=view) [edit]
> proposed patch
>
> This patch should restore the use of the previous stage compiler for plugins.
This is working fine in respect of putting the bootstrap compiler in and,
when --enable-build-with-cxx is given, the g++ plugins work on powerpc-darwin9.
When --enable-build-with-cxx is not given, several of them fail
(attribute_plugin-test-1, pragma_plugin-test-1, dumb-plugin-test-1).
This is because the compiler is ${objdir}/xgcc and the plugin names end ".c"
therefore they are built as standard "c".
If it is intended that plugins for g++ should be build-able as straight 'c',
then there is an issue the plugin examples.
otherwise, we need to arrange the the plugins get built by g++ when they are
intended to be used within it.
(this is not as simple as changing their filenames to end .C, since the
includes are defined in lib/plugin-support.exp and they don't include any
consideration of the possibility that c++ headers might be needed).
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42843
next prev parent reply other threads:[~2010-07-17 7:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 11:04 [Bug testsuite/42843] New: " amylaar at gcc dot gnu dot org
2010-01-23 0:00 ` [Bug testsuite/42843] " amylaar at gcc dot gnu dot org
2010-01-30 5:21 ` amylaar at gcc dot gnu dot org
2010-06-08 20:52 ` amylaar at gcc dot gnu dot org
2010-06-09 10:41 ` amylaar at gcc dot gnu dot org
2010-06-09 10:49 ` amylaar at gcc dot gnu dot org
2010-07-10 21:45 ` howarth at nitro dot med dot uc dot edu
2010-07-11 1:59 ` amylaar at gcc dot gnu dot org
2010-07-11 2:36 ` howarth at nitro dot med dot uc dot edu
2010-07-11 4:22 ` amylaar at gcc dot gnu dot org
2010-07-12 12:54 ` iains at gcc dot gnu dot org
2010-07-12 13:05 ` howarth at nitro dot med dot uc dot edu
2010-07-12 13:19 ` iains at gcc dot gnu dot org
2010-07-12 13:28 ` iains at gcc dot gnu dot org
2010-07-12 15:00 ` iains at gcc dot gnu dot org
2010-07-12 22:25 ` amylaar at gcc dot gnu dot org
2010-07-12 22:41 ` amylaar at gcc dot gnu dot org
2010-07-13 10:16 ` ro at CeBiTec dot Uni-Bielefeld dot DE
2010-07-13 13:06 ` howarth at nitro dot med dot uc dot edu
2010-07-14 20:23 ` amylaar at gcc dot gnu dot org
2010-07-16 8:40 ` iains at gcc dot gnu dot org
2010-07-17 7:20 ` iains at gcc dot gnu dot org [this message]
2010-09-02 15:10 ` ebotcazou at gcc dot gnu dot org
2010-09-03 16:03 ` ro at gcc dot gnu dot org
2010-09-18 8:54 ` ebotcazou 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=20100717072032.29182.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: 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).