public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "htl10 at users dot sourceforge dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/40912] 4.5 weekly snapshot: failed to pre-compile bits/stdc++.h.gch/O2ggnu++0x.gch Date: Thu, 30 Jul 2009 16:54:00 -0000 [thread overview] Message-ID: <20090730165446.22650.qmail@sourceware.org> (raw) In-Reply-To: <bug-40912-10503@http.gcc.gnu.org/bugzilla/> ------- Comment #9 from htl10 at users dot sourceforge dot net 2009-07-30 16:54 ------- (In reply to comment #7) > Do you want something to click? PR448 Oh, I didn't expect bug id that old to be relevant - I thought c/448 might be short for bug XX448 so I tried bug 40448 :-). (In reply to comment #8) > Subject: Re: 4.5 weekly snapshot: failed to pre-compile > bits/stdc++.h.gch/O2ggnu++0x.gch > > On Thu, 30 Jul 2009, paolo dot carlini at oracle dot com wrote: > > > As a side note, I want to mention that we are very close to finally fixing > > c/448 for 4.5.0. Then, any problem related to <stdint.h> will disappear. > > We're still quite some way from that; I just sent a list of 14 target OSes > that either need stdint.h information entered in GCC, or need to be > deprecated. (This is down from 20 at the start of April: information has > been added since then for Darwin, FreeBSD, HP-UX, Cygwin, MinGW and AIX.) > > http://gcc.gnu.org/ml/gcc/2009-07/msg00625.html > I can't say about the others alpha*-dec-osf[45]*, but I can certainly give you alphaev68-dec-osf5.1a . How do you like this info? If you have a list to hunt for, or even a small test program which includes the various headers and print the numbers, I can do that... See as I seem to be the only one submitting testsuite results for alpha*-dec-osf[45]* beyond 4.1-ish, what is the qualification/requirement for OS porter/maintainer to take it off the deprecated list? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40912
next prev parent reply other threads:[~2009-07-30 16:54 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-07-30 10:09 [Bug libstdc++/40912] New: " htl10 at users dot sourceforge dot net 2009-07-30 11:31 ` [Bug libstdc++/40912] " paolo dot carlini at oracle dot com 2009-07-30 11:50 ` htl10 at users dot sourceforge dot net 2009-07-30 12:41 ` paolo dot carlini at oracle dot com 2009-07-30 12:57 ` htl10 at users dot sourceforge dot net 2009-07-30 15:41 ` paolo dot carlini at oracle dot com 2009-07-30 15:59 ` htl10 at users dot sourceforge dot net 2009-07-30 16:26 ` paolo dot carlini at oracle dot com 2009-07-30 16:31 ` joseph at codesourcery dot com 2009-07-30 16:54 ` htl10 at users dot sourceforge dot net [this message] 2009-07-30 19:28 ` joseph at codesourcery dot com 2009-07-31 1:50 ` htl10 at users dot sourceforge dot net 2009-07-31 2:14 ` htl10 at users dot sourceforge dot net 2009-07-31 9:42 ` [Bug libstdc++/40912] [4.5 Regression] failure " paolo dot carlini at oracle dot com 2009-07-31 9:44 ` paolo dot carlini at oracle dot com 2009-07-31 9:49 ` paolo dot carlini at oracle dot com 2009-07-31 9:55 ` htl10 at users dot sourceforge dot net 2009-07-31 12:19 ` paolo at gcc dot gnu dot org 2009-07-31 12:22 ` paolo dot carlini at oracle dot com 2009-08-02 22:34 ` htl10 at users dot sourceforge dot net 2009-08-02 22:51 ` htl10 at users dot sourceforge dot net 2009-08-02 23:36 ` paolo at gcc dot gnu dot org 2009-08-02 23:38 ` paolo dot carlini at oracle dot com
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=20090730165446.22650.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).