[Bug pch/17162] warning about invalid precompiled header even if the correct one is used

2019-10-05 Thread guriev-ns at ya dot ru
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=17162 Nicholas Guriev changed: What|Removed |Added CC||guriev-ns at ya dot ru --- Comment #4

[Bug pch/91999] pch_open_file picks up a first found precompiled header even if it's not suitable

2019-10-05 Thread guriev-ns at ya dot ru
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91999 Nicholas Guriev changed: What|Removed |Added Resolution|INVALID |DUPLICATE --- Comment #3 from Nicholas

[Bug pch/91999] pch_open_file picks up a first found precompiled header even if it's not suitable

2019-10-05 Thread guriev-ns at ya dot ru
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91999 --- Comment #2 from Nicholas Guriev --- Thank you for the clarification. The diagnostic message looks like no pch is used at all that results in a misunderstanding. At an end-user point of view, the -Winvalid-pch flag isn't so valuable. Who care

[Bug pch/91999] New: pch_open_file picks up a first found precompiled header even if it's not suitable

2019-10-05 Thread guriev-ns at ya dot ru
IRMED Severity: normal Priority: P3 Component: pch Assignee: unassigned at gcc dot gnu.org Reporter: guriev-ns at ya dot ru Target Milestone: --- In the following example g++ uses C precompiled header if it exists, although there is a C++ precompiled header near

[Bug c/78970] New: GCC crashes if input file is dash

2017-01-02 Thread guriev-ns at ya dot ru
Assignee: unassigned at gcc dot gnu.org Reporter: guriev-ns at ya dot ru Target Milestone: --- GCC with an input file as hyphen crashes when it tries to process a C/C++ header. But it perfectly works if the argument is a normal file name (even link `/dev/stdin`). mymedia@comp2:/tmp