public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marc.glisse at normalesup dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/50167] New: gmp memory functions are extern "C" (graphite) Date: Tue, 23 Aug 2011 15:53:00 -0000 [thread overview] Message-ID: <bug-50167-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50167 Bug #: 50167 Summary: gmp memory functions are extern "C" (graphite) Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap AssignedTo: unassigned@gcc.gnu.org ReportedBy: marc.glisse@normalesup.org Hello, with gcc moving to C++, a few things need adapting. In particular, when asking for the gmp memory functions, this: void (*gmp_free) (void *, size_t); mp_get_memory_functions (NULL, NULL, &gmp_free); becomes wrong. One should have somewhere (protected by tests on __cplusplus since we are still building with C compilers): extern "C" { typedef void (*mytype) (void *, size_t); } And then: mytype gmp_free; mp_get_memory_functions (NULL, NULL, &gmp_free); g++ can't see the difference (yet? see Bug 2316), but some other compilers can (sunpro), and we want other C++ compilers to be usable for stage1. This code appears in 2 files: ./gcc/graphite-ppl.c ./gcc/graphite-interchange.c
next reply other threads:[~2011-08-23 15:51 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-08-23 15:53 marc.glisse at normalesup dot org [this message] 2011-08-24 8:20 ` [Bug bootstrap/50167] " rguenth at gcc dot gnu.org 2012-08-13 6:17 ` glisse at gcc dot gnu.org 2013-01-03 20:07 ` glisse at gcc dot gnu.org 2013-01-03 20:11 ` glisse at gcc dot gnu.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=bug-50167-4@http.gcc.gnu.org/bugzilla/ \ --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).