public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Geoff Keating <geoffk@geoffk.org> To: geoffk@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: other/9274: [pch] cannot create libstdc++-v3 pch Date: Mon, 14 Apr 2003 22:06:00 -0000 [thread overview] Message-ID: <20030414220600.18815.qmail@sources.redhat.com> (raw) The following reply was made to PR other/9274; it has been noted by GNATS. From: Geoff Keating <geoffk@geoffk.org> To: bkoz@gcc.gnu.org, bkoz@redhat.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, geoffk@gcc.gnu.org, geoffk@geoffk.org, jason@redhat.com, pcarlini@unitus.it, gcc-gnats@gcc.gnu.org Cc: bkoz@redhat.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, geoffk@geoffk.org, jason@redhat.com, pcarlini@unitus.it Subject: Re: other/9274: [pch] cannot create libstdc++-v3 pch Date: Mon, 14 Apr 2003 15:02:15 -0700 The original reported bug does work on Darwin, as does running make-check-target-libstdc++-v3 after running make stamp-stdc++-precompile. Of course, Darwin doesn't use DWARF2. This patch might help. Try it and see what happens. -- - Geoffrey Keating <geoffk@geoffk.org> ===File ~/patches/apple/gcc-pchdecluid.patch================ *** tree.c.~1.295.~ Fri Apr 11 19:01:38 2003 --- tree.c Mon Apr 14 14:56:53 2003 *************** *** 92,100 **** #endif /* GATHER_STATISTICS */ /* Unique id for next decl created. */ ! static int next_decl_uid; /* Unique id for next type created. */ ! static int next_type_uid = 1; /* Since we cannot rehash a type after it is in the table, we have to keep the hash code. */ --- 92,100 ---- #endif /* GATHER_STATISTICS */ /* Unique id for next decl created. */ ! static GTY(()) int next_decl_uid; /* Unique id for next type created. */ ! static GTY(()) int next_type_uid = 1; /* Since we cannot rehash a type after it is in the table, we have to keep the hash code. */ ============================================================
next reply other threads:[~2003-04-14 22:06 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-14 22:06 Geoff Keating [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-04-16 0:30 geoffk 2003-04-15 22:56 Paolo Carlini 2003-04-15 22:46 Benjamin Kosnik 2003-04-15 20:56 Geoff Keating 2003-04-15 15:46 Benjamin Kosnik 2003-04-14 19:16 bkoz 2003-04-10 21:51 bkoz 2003-03-25 18:06 bkoz 2003-02-22 0:46 Geoffrey Keating 2003-02-06 21:25 bkoz
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=20030414220600.18815.qmail@sources.redhat.com \ --to=geoffk@geoffk.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=geoffk@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).