[Bug c/58988] New: -Werror=missing-include-dirs does not work

[Bug c/58988] New: -Werror=missing-include-dirs does not work

[bugzilla@poradnik-webmastera.com]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58988

            Bug ID: 58988
           Summary: -Werror=missing-include-dirs does not work
           Product: gcc
           Version: 4.7.3
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: bugzilla@poradnik-webmastera.com

I tried to pass -Werror=missing-include-dirs option to gcc in order to find all
non-existing include dirs and found that this option in broken. In gcc 4.5.2
this option is ignored - gcc does not print any message when non-existing
include dir is specified. gcc 4.7.3 prints warning only.

gcc (both tested versions) changes this warnings into errors when both
-Wmissing-include-dirs -Werror options are used, but this is not an option for
be because of other warnings which are in my code.

I tested this using following command:
g++ -c test.cc -o test.o -I/a -Werror=missing-include-dirs

[Bug c/58988] -Werror=missing-include-dirs does not work

[bugzilla@poradnik-webmastera.com]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58988

--- Comment #1 from Daniel Fruzynski <bugzilla@poradnik-webmastera.com> ---
gcc 4.8.2 is also affected by this bug - is works in the same way as gcc 4.7.3.

[Bug c/58988] -Werror=missing-include-dirs does not work

[manu at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58988

Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |manu at gcc dot gnu.org

--- Comment #2 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
I think this should fix it, but I haven't even tried to compile it.

Index: incpath.c
===================================================================
--- incpath.c   (revision 204219)
+++ incpath.c   (working copy)
@@ -261,11 +261,12 @@ remove_duplicates (cpp_reader *pfile, st
          else
            {
              /* If -Wmissing-include-dirs is given, warn.  */
              cpp_options *opts = cpp_get_options (pfile);
              if (opts->warn_missing_include_dirs && cur->user_supplied_p)
-               cpp_errno (pfile, CPP_DL_WARNING, cur->name);
+               cpp_warning (pfile, CPP_W_MISSING_INCLUDE_DIRS, "%s: %s",
+                            cur->name, xstrerror (errno));
              reason = REASON_NOENT;
            }
        }
       else if (!S_ISDIR (st.st_mode))
        cpp_error_with_line (pfile, CPP_DL_WARNING, 0, 0,

A better fix is probably to add a variant of cpp_errno that takes a reason like
cpp_warning does. The current cpp_errno will then call this new variant with
CPP_W_NONE. These should be added to libcpp/errors.c and exported from
libcpp/include/cpplib.h

This should be an easy hack for someone to start contributing to GCC.
>From gcc-bugs-return-433686-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Nov 06 07:30:27 2013
Return-Path: <gcc-bugs-return-433686-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16401 invoked by alias); 6 Nov 2013 07:30:27 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 15127 invoked by uid 48); 6 Nov 2013 07:28:24 -0000
From: "bernd.edlinger at hotmail dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/58970] [4.7/4.8/4.9 Regression] internal compiler error: in get_bit_range, at expr.c:4562
Date: Wed, 06 Nov 2013 07:30:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 4.8.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bernd.edlinger at hotmail dot de
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.7.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-58970-4-cRPvVDjlG3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-58970-4@http.gcc.gnu.org/bugzilla/>
References: <bug-58970-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2013-11/txt/msg00463.txt.bz2
Content-length: 735

http://gcc.gnu.org/bugzilla/show_bug.cgi?idX970

--- Comment #26 from Bernd Edlinger <bernd.edlinger at hotmail dot de> ---
(In reply to Jakub Jelinek from comment #25)
> (In reply to Bernd Edlinger from comment #24)
> > Created attachment 31169 [details]
> > Another (better) attempt at fixing this ICE.
> >
> > This avoids any negative bitpos from get_inner_reference.
> > These negative bitpos values are just _very_ dangerous all the
> > way down to expmed.c
>
> I disagree that it is better, you are forgetting get_inner_reference has
> other > 20 callers outside of expansion and there is no reason why negative
> bitpos would be a problem in those cases.

Please, give me one example of _valid_ C where bitpos is negative.

[Bug c/58988] -Werror=missing-include-dirs does not work

[manu at gcc dot gnu.org]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="UTF-8", Size: 3084 bytes --]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58988

Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2014-04-13
     Ever confirmed|0                           |1

--- Comment #3 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
This is confirmed, just waiting for someone to implement the fix.
>From gcc-bugs-return-448917-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Apr 13 15:04:59 2014
Return-Path: <gcc-bugs-return-448917-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25981 invoked by alias); 13 Apr 2014 15:04:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 25966 invoked by uid 48); 13 Apr 2014 15:04:56 -0000
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/60832] New: add pretty-printer code for double-int/wide-int
Date: Sun, 13 Apr 2014 15:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 4.10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: manu at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter attachments.created
Message-ID: <bug-60832-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-04/txt/msg00937.txt.bz2
Content-length: 740

http://gcc.gnu.org/bugzilla/show_bug.cgi?id`832

            Bug ID: 60832
           Summary: add pretty-printer code for double-int/wide-int
           Product: gcc
           Version: 4.10.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: middle-end
          Assignee: unassigned at gcc dot gnu.org
          Reporter: manu at gcc dot gnu.org

Created attachment 32590
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id2590&actioníit
WIP patch

Currently, there is no pretty-printer code to print a double-int (or wide-int)
in a warning. This would be useful for cases such as the one in the attached
patch. The current method prints '3u' instead of just '3', as it should.