public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ian at wasabisystems dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug pch/14940] New: PCH largefile test fails on various platforms Date: Tue, 13 Apr 2004 14:48:00 -0000 [thread overview] Message-ID: <20040413135721.14940.ian@wasabisystems.com> (raw) The PCH largefile test, in gcc/testsuite/gcc.dg/pch/pch.exp, fails using the default mmap implementation on i386-unknown-netbsdelf1.6.1. It also fails using the Solaris implementation on sparc-sun-solaris2.9. It fails on i686-pc-cygwin, although actually most of the PCH tests fail on that platform. A failure in the PCH largefile test for a given platform means that PCH is unstable for that platform. A PCH will work for most source code files but will fail for large source code files. The user can not easily predict when a PCH will work and when it will fail. When a PCH fails, there is no easy way to compile the file without removing the PCH so that gcc does not find it. On i386-unknown-netbsdelf1.6.1, and probably other platforms, a direct consequence is that qt-x11-free-3.3.0 can not be built. Those sources test whether PCH works, and use it if they do. The test passes, but some of the source files are large. Those source files fail to build. -- Summary: PCH largefile test fails on various platforms Product: gcc Version: 3.5.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: pch AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: ian at wasabisystems dot com CC: gcc-bugs at gcc dot gnu dot org GCC host triplet: i386-unknown-netbsdelf1.6.1 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14940
next reply other threads:[~2004-04-13 13:57 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-04-13 14:48 ian at wasabisystems dot com [this message] 2004-04-13 16:35 ` [Bug pch/14940] " ebotcazou at gcc dot gnu dot org 2004-04-13 16:55 ` pinskia at gcc dot gnu dot org 2004-04-13 19:48 ` geoffk at gcc dot gnu dot org 2004-04-14 18:49 ` ljrittle at gcc dot gnu dot org 2004-07-17 4:09 ` pinskia at gcc dot gnu dot org 2004-07-17 4:10 ` pinskia at gcc dot gnu dot org 2004-07-17 4:21 ` dave at hiauly1 dot hia dot nrc dot ca 2004-07-17 14:20 ` ian at wasabisystems dot com 2004-07-17 14:43 ` ian at wasabisystems dot com 2004-07-17 15:43 ` ebotcazou at gcc dot gnu dot org 2004-07-17 17:10 ` dave at hiauly1 dot hia dot nrc dot ca 2004-07-18 10:00 ` ebotcazou at gcc dot gnu dot org 2004-07-18 12:26 ` ian at wasabisystems dot com 2004-07-18 16:03 ` dave at hiauly1 dot hia dot nrc dot ca 2004-07-20 17:49 ` pinskia at gcc dot gnu dot org 2004-08-21 17:05 ` pinskia at gcc dot gnu dot org 2004-08-31 14:20 ` dave at hiauly1 dot hia dot nrc dot ca 2004-10-12 19:56 ` jgrimm2 at us dot ibm dot com 2004-11-04 4:57 ` phython at gcc dot gnu dot org 2004-11-04 7:09 ` ebotcazou at gcc dot gnu dot org 2004-11-09 12:35 ` cvs-commit at gcc dot gnu dot org 2004-11-23 2:30 ` cvs-commit at gcc dot gnu dot org 2004-11-27 16:57 ` cvs-commit at gcc dot gnu dot org 2004-11-30 3:11 ` cvs-commit 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=20040413135721.14940.ian@wasabisystems.com \ --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).