Bug 447833
Summary: | cpp adds extraneous blank lines at beginning of output | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | JW <ohtmvyyn> |
Component: | gcc | Assignee: | Jakub Jelinek <jakub> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 8 | Keywords: | Reopened |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-05-29 14:38:57 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
JW
2008-05-22 01:33:32 UTC
cpp never makes any whitespace guarantees. Yes, it does.
> When GCC is given the `-traditional-cpp' option, it attempts to emulate a
> traditional preprocessor.
And how is that relevant to this? You are not using -traditional-cpp, nor this describes how traditional preprocessor should behave. Yes, I was also using -traditional-cpp but I inadvertently forgot to say so. There could be a bug in my bug entry mechanism. But that mechanism never makes any guarantees about accuracy. Also, cpp -P -C also adds the two extra lines. So the bug manifests itself in a variety of ways. Find the cause of this bug and you might find something bigger. Are you sure you wont? As I said, cpp never does try to preserve the whitespace, never did. When you use -P you simply mean you don't care about mapping lines back to the original source. The two lines in the beginning in particular come from the builtin defines (try e.g. preprocessing with -dM to see what is there). Please stop reopening this. |