[Bug preprocessor/55115] [4.9/5/6 Regression] missing headers as fatal breaks cproto logic

2016-01-21 Thread Robert.Gomes at igt dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55115

--- Comment #18 from RGomes  ---
The cproto design and usage is not broken. Everyone here agrees that a missing
include during "compilation" rightfully should generate an error. It is the
"preprocessor behavior only" where we are asking for tolerance for a missing
include. Why? Because a .h file that contains only function prototypes is being
generated ahead of the compilation (cproto is doing this step, using the gcc
preprocessor) - then later, that generated .h file "will" be present during
compilation. This is just one use case - there are others - so the request
being made is only for the preprocessor eliminating this error - not
compilation. (Followup to my earlier post - my present workaround was
reluctantly installing 2 gcc compilers: a 4.4 compatible one invoked for
prototyping only, and the latest gcc for compilation).

[Bug driver/19541] need another option to support what -I- did just besides -iquote

2016-01-08 Thread Robert.Gomes at igt dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19541

RGomes  changed:

   What|Removed |Added

 CC||Robert.Gomes at igt dot com

--- Comment #25 from RGomes  ---
I also vote for preserving the -I- original behavior, i.e. simply get rid of
the deprecation message from the precompiler. We also have situations where
code is pulled in from other directories and vpath is in play, and these sort
of use cases rely on the behavior provided by -I-, despite the original
motivation behind wanting to deprecate it. Thanks.

[Bug preprocessor/55115] [4.9/5/6 Regression] missing headers as fatal breaks cproto logic

2015-09-01 Thread Robert.Gomes at igt dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55115

RGomes  changed:

   What|Removed |Added

 CC||Robert.Gomes at igt dot com

--- Comment #16 from RGomes  ---
Hi,

I have watched this thread for years expecting a switch to be introduced to
allow the former GCC behavior of tolerating missing header files and I can no
longer remain on the side lines.  I echo the sentiment of others that the
ability to permit missing headers is something we rely on to auto-generate said
header files using cproto, and we've been doing this as far back as GCC 3.x. 
Of course missing headers should be an error during compilation, but
pre-compile it is natural to auto-generate a variety of header files, at least
in our situation. I find myself having to downgrade to GCC 4.4.7 in order to
work around this issue, but I would prefer to continue to use future editions
of GCC.  Please see if a safety valve can be put in to allow the former
behavior, it seems like this issue keeps getting bumped to future revisions but
at some point we are going to be between a rock and a hard place with decisions
about OS and GCC upgrades.  Thank you for your anticipated consideration.