public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/20348] [4.0/4.1 Regression] File not included when file with same name is included before Date: Fri, 26 Aug 2005 16:16:00 -0000 [thread overview] Message-ID: <20050826155758.19141.qmail@sourceware.org> (raw) In-Reply-To: <20050306130835.20348.pepster@users.sourceforge.net> ------- Additional Comments From jakub at gcc dot gnu dot org 2005-08-26 15:57 ------- This got broken by the libcpp/files.c part of http://gcc.gnu.org/ml/gcc-patches/2004-06/msg00272.html My understanding of the change was that this was just a performance improvement. The question is if that change is fixable to handle this and keep the improvements where they can be used, or if it should be reverted. -- What |Removed |Added ---------------------------------------------------------------------------- CC| |bje at gcc dot gnu dot org, | |zackw at panix dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20348
next prev parent reply other threads:[~2005-08-26 15:58 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-03-06 13:08 [Bug preprocessor/20348] New: " pepster at users dot sourceforge dot net 2005-03-06 13:09 ` [Bug preprocessor/20348] " pepster at users dot sourceforge dot net 2005-03-06 15:34 ` [Bug preprocessor/20348] [4.0/4.1 Regression] " pinskia at gcc dot gnu dot org 2005-04-15 13:22 ` pinskia at gcc dot gnu dot org 2005-04-21 5:00 ` mmitchel at gcc dot gnu dot org 2005-07-08 1:38 ` mmitchel at gcc dot gnu dot org 2005-07-09 21:58 ` pepster at users dot sourceforge dot net 2005-08-26 16:16 ` jakub at gcc dot gnu dot org [this message] 2005-08-27 5:44 ` Neil Booth 2005-08-26 16:18 ` jakub at gcc dot gnu dot org 2005-08-27 6:18 ` neil at daikokuya dot co dot uk 2005-08-30 6:36 ` cvs-commit at gcc dot gnu dot org 2005-08-30 6:36 ` cvs-commit at gcc dot gnu dot org 2005-08-30 10:56 ` pinskia 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=20050826155758.19141.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).