--- Additional Comments From steven at gcc dot gnu dot org 2005-02-09
10:37 ---
I don't see why this is critical.
--
What|Removed |Added
Severity|critical
--- Additional Comments From prj-bugzilla-gcc at multivac dot cwru dot edu
2004-12-13 19:10 ---
Ok, bug preprocessor/6521 looks like it had the same symptom I see now with 3.4.
Neil and Zack didn't think it was worth fixing at first, but it did get fixed,
and managed to stay fixed
--- Additional Comments From james at juranfamily dot org 2004-12-13 18:43
---
I believe the bug Neil referred to in comment #7 is bug preprocessor/6521 from
May 2002.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15220
--- Additional Comments From ebotcazou at gcc dot gnu dot org 2004-12-05
09:35 ---
Neil, would you mind updating the status of this bug so that it doesn't appear
as a critical regression against 3.4.x and 4.0? If the observed behaviour is
the intended one, please close the bug as
--- Additional Comments From prj-bugzilla-gcc at multivac dot cwru dot edu
2004-12-05 22:40 ---
3.4 is a lost cause by this point, but I'd really like to see this fixed for
4.0. My build system needs this to track dependencies. What exactly was agreed
before - the lack of the warning,
--- Additional Comments From neroden at gcc dot gnu dot org 2004-11-27
23:18 ---
Ow. The dependencies are emitted in open_file_failed in libcpp/files.c; but
that routine *doesn't know* whether the file was called for in a or a
directive.
Fixing this requires some restructuring
--- Additional Comments From neil at daikokuya dot co dot uk 2004-11-28
00:50 ---
Subject: Re: [3.3/3.4/4.0 regression] gcc -E -MM -MG reports missing system
headers in source directory
neroden at gcc dot gnu dot org wrote:-
--- Additional Comments From neroden at gcc dot gnu
--- Additional Comments From mmitchel at gcc dot gnu dot org 2004-11-01 00:44
---
Postponed until GCC 3.4.4.
--
What|Removed |Added
Target Milestone|3.4.3
