public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "matz at suse dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/19985] [3.4/4.0/4.1 Regression] executables created with -fprofile-arcs -ftest-coverage segfault in gcov_exit () Date: Tue, 21 Jun 2005 20:31:00 -0000 [thread overview] Message-ID: <20050621203122.17540.qmail@sourceware.org> (raw) In-Reply-To: <20050215214329.19985.lothar@xcerla.com> ------- Additional Comments From matz at suse dot de 2005-06-21 20:31 ------- This patch seems to be the reason for warnings like: In file included from ../../gcc/gcov-io.h:239, from ../../gcc/libgcov.c:51: ./auto-host.h:23:1: warning: "DEFAULT_USE_CXA_ATEXIT" redefined In file included from ./tm.h:12, from ../../gcc/libgcov.c:39: ../../gcc/defaults.h:712:1: warning: this is the location of the previous definition There are now many warnings of this type during building gcc. This is because auto-host.h is now included, but _after_ all the other headers, which do something like #ifndef BLA #define BLA ... #endif Because auto-host.h is not yet included there, BLA is not defined, so the default will be defined, and then auto-host.h is included leading to double definitions. libgcov.c talks about not able to include <config.h> because that's for the host, not for the target. So I don't know if auto-host.h (also for the host) should be included at all. But if it is, then it has to be earlier. Perhaps in libgcov.c directly as first file. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19985
prev parent reply other threads:[~2005-06-21 20:31 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-02-16 3:32 [Bug c++/19985] New: " lothar at xcerla dot com 2005-02-16 3:32 ` [Bug middle-end/19985] " pinskia at gcc dot gnu dot org 2005-02-16 3:37 ` lothar at xcerla dot com 2005-02-16 3:48 ` pinskia at gcc dot gnu dot org 2005-03-01 1:03 ` lothar at xcerla dot com 2005-03-01 1:16 ` pinskia at gcc dot gnu dot org 2005-03-01 1:23 ` lothar at xcerla dot com 2005-03-08 3:59 ` renierm at us dot ibm dot com 2005-03-08 14:52 ` pinskia at gcc dot gnu dot org 2005-03-10 19:42 ` janis at gcc dot gnu dot org 2005-03-11 1:32 ` janis at gcc dot gnu dot org 2005-03-11 23:54 ` janis at gcc dot gnu dot org 2005-03-15 17:22 ` [Bug middle-end/19985] [3.4/4.0/4.1 Regression] " pinskia at gcc dot gnu dot org 2005-03-25 0:09 ` janis at gcc dot gnu dot org 2005-04-21 5:01 ` mmitchel at gcc dot gnu dot org 2005-05-02 18:03 ` cvs-commit at gcc dot gnu dot org 2005-05-02 18:05 ` cvs-commit at gcc dot gnu dot org 2005-05-02 18:09 ` cvs-commit at gcc dot gnu dot org 2005-05-02 19:02 ` pinskia at gcc dot gnu dot org 2005-06-21 20:31 ` matz at suse dot de [this message]
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=20050621203122.17540.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).