This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

preprocessor/7029: preprocessor should ignore #warning with -M


>Number:         7029
>Category:       preprocessor
>Synopsis:       preprocessor should ignore #warning with -M
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Fri Jun 14 04:26:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Wolfgang Bangerth
>Release:        unknown-1.0
>Organization:
>Environment:
all
>Description:
IMHO, warnings generated by #warning may be omitted when not
actually compiling code, for example when using -M to
generate dependency lists. They seem inappropriate for this
task.
>How-To-Repeat:
program> echo "#warning Warn about something" > x.cc
program> gcc -M x.cc 
x.cc:1:2: warning: #warning Warn about something
x.o: x.cc
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]