public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/15167] [3.4/4.0 Regression] Internal compiler error with "#pragma once"
Date: Mon, 06 Dec 2004 07:12:00 -0000	[thread overview]
Message-ID: <20041206071157.25348.qmail@sourceware.org> (raw)
In-Reply-To: <20040427115120.15167.Roland.Meub@Tenovis.com>


------- Additional Comments From ebotcazou at gcc dot gnu dot org  2004-12-06 07:11 -------
> Eric - can you try your testcase on GCC sources as of around the beginning of
> August 2003?

You can't reasonably ask this.  It is your duty as a cpplib maintainer to do
this kind of work.  I honestly have no time to do it myself.

> This is when I completely rewrote the whole file lookup mechanism, and
> contrary to Zack's claims it did work 100% correctly, to the best of my
> knowledge, and would always get links, both hard and soft, correct with
> #pragma once correct no matter how contorted or renamed the file was.  Then
> only issue in that code was the -remap bug that has since been fixed.

Yes, the code doesn't look particularly broken to me.  Does your original code
reset buffer_valid when the buffer is freed?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15167


  parent reply	other threads:[~2004-12-06  7:12 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-27 11:56 [Bug preprocessor/15167] New: " Roland dot Meub at Tenovis dot com
2004-04-27 12:46 ` [Bug preprocessor/15167] [3.4/3.5 Regression] " pinskia at gcc dot gnu dot org
2004-04-27 12:48 ` Roland dot Meub at Tenovis dot com
2004-04-27 13:08 ` pinskia at gcc dot gnu dot org
2004-04-27 13:36 ` pinskia at gcc dot gnu dot org
2004-04-28 17:01 ` ossama at dre dot vanderbilt dot edu
2004-04-28 17:01 ` ossama at dre dot vanderbilt dot edu
2004-06-15 14:35 ` chucky at outmax dot org
2004-06-15 14:40 ` pinskia at gcc dot gnu dot org
2004-06-22  8:08 ` mmitchel at gcc dot gnu dot org
2004-08-29 18:12 ` mmitchel at gcc dot gnu dot org
2004-08-29 18:16 ` mmitchel at gcc dot gnu dot org
2004-10-11  5:22 ` [Bug preprocessor/15167] [3.4/4.0 " pinskia at gcc dot gnu dot org
2004-10-13 11:31 ` pinskia at gcc dot gnu dot org
2004-11-01  0:47 ` mmitchel at gcc dot gnu dot org
2004-11-12  4:54 ` pinskia at gcc dot gnu dot org
2004-12-02 18:55 ` ebotcazou at gcc dot gnu dot org
2004-12-05 18:48 ` pinskia at gcc dot gnu dot org
2004-12-06  2:27 ` neil at gcc dot gnu dot org
2004-12-06  7:12 ` ebotcazou at gcc dot gnu dot org [this message]
2004-12-09  7:07 ` ebotcazou at gcc dot gnu dot org
2004-12-15 13:31 ` cvs-commit at gcc dot gnu dot org
2004-12-15 13:42 ` cvs-commit at gcc dot gnu dot org
2004-12-15 13:43 ` ebotcazou 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=20041206071157.25348.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: link
Be 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).