public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "persgray at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/66902] _S_debug_messages is unneccessary public
Date: Fri, 11 Sep 2015 11:13:00 -0000	[thread overview]
Message-ID: <bug-66902-4-AILlEFtEQ7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66902-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Vadim Zhukov <persgray at gmail dot com> ---
(In reply to Jonathan Wakely from comment #6)
> 3.5 [basic.link]:
> 
> -3-  A name having namespace scope (3.3.6) has internal linkage if it is the
>      name of
>       — a variable, function or function template that is explicitly declared
>         static; or,
>       — a variable of non-volatile const-qualified type that is neither
>         explicitly declared extern nor previously declared to have external
>         linkage; or
>       — a data member of an anonymous union.
> 
> The first bullet applied when it was explicitly declared static and the
> second bullet applies now that it is a const-qualified type at namespace
> scope. In both cases it has internal linkage, so you should not see a global
> symbol and should not get the warning.

Sorry, I've missed that. Thank you for clarification.
>From gcc-bugs-return-496957-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Sep 11 11:15:18 2015
Return-Path: <gcc-bugs-return-496957-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104369 invoked by alias); 11 Sep 2015 11:15: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 104300 invoked by uid 48); 11 Sep 2015 11:15:15 -0000
From: "olegendo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/58517] ifcvt (after combine) puts ccreg clobbering insn between ccset insn and ccreg use
Date: Fri, 11 Sep 2015 11:15:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: olegendo at gcc dot gnu.org
X-Bugzilla-Status: NEW
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:
Message-ID: <bug-58517-4-FjDXbKXpCy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-58517-4@http.gcc.gnu.org/bugzilla/>
References: <bug-58517-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-09/txt/msg00935.txt.bz2
Content-length: 420

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

--- Comment #7 from Oleg Endo <olegendo at gcc dot gnu.org> ---
(In reply to ktkachov from comment #6)
> Huh, I wasn't aware of this BZ.
> This looks eerily similar to what I think is the root cause of PR 67481,
> which I'm working on now.
>
> After I'm done with PR 67481 it would be interesting to have a look whether
> they are indeed the same issue

OK, thanks!


      parent reply	other threads:[~2015-09-11 11:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-17  2:18 [Bug libstdc++/66902] New: " persgray at gmail dot com
2015-07-17  9:13 ` [Bug libstdc++/66902] " redi at gcc dot gnu.org
2015-08-26 21:01 ` redi at gcc dot gnu.org
2015-09-03 19:05 ` redi at gcc dot gnu.org
2015-09-11 10:09 ` persgray at gmail dot com
2015-09-11 10:38 ` redi at gcc dot gnu.org
2015-09-11 11:13 ` persgray at gmail dot com [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-66902-4-AILlEFtEQ7@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).