[Bug c/68029] New: Strange behavior of -fdiagnostics-color option

[Bug c/68029] New: Strange behavior of -fdiagnostics-color option

[EngyCZ at gmail dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68029

            Bug ID: 68029
           Summary: Strange behavior of -fdiagnostics-color option
           Product: gcc
           Version: 6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: EngyCZ at gmail dot com
  Target Milestone: ---

Hi.
  In current trunk version of GCC 6.0 compiler I have found strange behavior of
-fdiagnostics-color option

gcc.exe -fdiagnostics-color=never a.c
will output colored error: a.c: No such file or directory

gcc.exe  a.c -fdiagnostics-color=never
will output not colored error: a.c: No such file or directory

gcc --version
gcc (GCC) 6.0.0 20151020 (experimental)

[Bug driver/68029] Strange behavior of -fdiagnostics-color option

[mpolacek at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68029

Marek Polacek <mpolacek at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2015-10-22
                 CC|                            |mpolacek at gcc dot gnu.org
          Component|c                           |driver
     Ever confirmed|0                           |1

--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Confirmed.

[Bug driver/68029] Strange behavior of -fdiagnostics-color option

[manu at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68029

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> ---
What does -### show for the call to cc1 ? My commit r228094 to opts-common.c
should have fixed this.
>From gcc-bugs-return-500335-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Oct 22 21:18:40 2015
Return-Path: <gcc-bugs-return-500335-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82959 invoked by alias); 22 Oct 2015 21:18:37 -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 82742 invoked by uid 48); 22 Oct 2015 21:18:33 -0000
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/68052] No printf format warnings in C++ code for macro in system headers
Date: Thu, 22 Oct 2015 21:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 5.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: manu at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
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_status cc resolution
Message-ID: <bug-68052-4-S89v2GLOIv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-68052-4@http.gcc.gnu.org/bugzilla/>
References: <bug-68052-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-10/txt/msg01890.txt.bz2
Content-length: 737

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68052

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |manu at gcc dot gnu.org
         Resolution|---                         |DUPLICATE

--- Comment #1 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
The differences that you observe are because C and C++ give the warnings at
different locations. I think the location used by C++ is wrong.

*** This bug has been marked as a duplicate of bug 56856 ***
>From gcc-bugs-return-500336-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Oct 22 21:18:40 2015
Return-Path: <gcc-bugs-return-500336-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83027 invoked by alias); 22 Oct 2015 21:18:40 -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 82900 invoked by uid 48); 22 Oct 2015 21:18:35 -0000
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/56856] the location of Wformat warnings points *after* the format string
Date: Thu, 22 Oct 2015 21:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: manu at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
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: cc
Message-ID: <bug-56856-4-sVxOQzyAFX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-56856-4@http.gcc.gnu.org/bugzilla/>
References: <bug-56856-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-10/txt/msg01891.txt.bz2
Content-length: 477

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56856

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |gcc at blino dot org

--- Comment #2 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
*** Bug 68052 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-500337-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Oct 22 21:21:31 2015
Return-Path: <gcc-bugs-return-500337-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86601 invoked by alias); 22 Oct 2015 21:21:31 -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 86517 invoked by uid 48); 22 Oct 2015 21:21:26 -0000
From: "dmorilha at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/68058] New: _GLIBCXX_BEGIN_NAMESPACE_VERSION breaks regex
Date: Thu, 22 Oct 2015 21:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 5.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmorilha at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
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 target_milestone
Message-ID: <bug-68058-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-10/txt/msg01892.txt.bz2
Content-length: 1355

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68058

            Bug ID: 68058
           Summary: _GLIBCXX_BEGIN_NAMESPACE_VERSION breaks regex
           Product: gcc
           Version: 5.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: dmorilha at gmail dot com
  Target Milestone: ---

when compiling libstdc++ with --enable-symvers=gnu-versioned-namespace
std::regex complaining about private data members trying to be accessed outside
the class:

22:55:46 /home/y/include/c++/4.9.2/bits/regex.h:796:30: error:
‘std::__7::basic_regex<char>::_AutomatonPtr
std::__7::basic_regex<char>::_M_automaton’ is protected
22:55:46        _AutomatonPtr          _M_automaton;

I believe the bug is related with the __detail namespace[1] and friend
classes[2] as it lacks the NAMESPACE_VERSION expansion. This happens in other
lines and I believe it extends to hashmap as well. Turning data members public
"fixes" the compilation problem.

[1]:
https://github.com/gcc-mirror/gcc/blob/e0f174323b4297f46d9109201666da42aaa55fc8/libstdc%2B%2B-v3/include/bits/regex.h#L46

[2]:
https://github.com/gcc-mirror/gcc/blob/e0f174323b4297f46d9109201666da42aaa55fc8/libstdc%2B%2B-v3/include/bits/regex.h#L772
>From gcc-bugs-return-500338-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Oct 22 21:39:20 2015
Return-Path: <gcc-bugs-return-500338-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118570 invoked by alias); 22 Oct 2015 21:39:18 -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 118542 invoked by uid 48); 22 Oct 2015 21:39:14 -0000
From: "nsz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/68059] New: [arm] libgcc uses __write to report error
Date: Thu, 22 Oct 2015 21:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 5.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: nsz at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
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 target_milestone
Message-ID: <bug-68059-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: 2015-10/txt/msg01893.txt.bz2
Content-length: 817

https://gcc.gnu.org/bugzilla/show_bug.cgi?idh059

            Bug ID: 68059
           Summary: [arm] libgcc uses __write to report error
           Product: gcc
           Version: 5.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: nsz at gcc dot gnu.org
  Target Milestone: ---

this bug was reported on the musl libc list:
http://www.openwall.com/lists/musl/2015/10/22/3

libgcc/config/arm/linux-atomic-64bit.c references __write
in __check_for_sync8_kernelhelper.

__write is not a public abi symbol in libc, libgcc should not
reference it.

the standard way is to use assert, but in this case the error
message seems superfluous: the crash is in a ctor, easily
reproducible.