public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ppluzhnikov at google dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/56947] New: [4.7.3 regression] Bogus 'XX' was not declared in this scope
Date: Sat, 13 Apr 2013 16:06:00 -0000	[thread overview]
Message-ID: <bug-56947-4@http.gcc.gnu.org/bugzilla/> (raw)


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

             Bug #: 56947
           Summary: [4.7.3 regression] Bogus 'XX' was not declared in this
                    scope
    Classification: Unclassified
           Product: gcc
           Version: 4.7.3
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: ppluzhnikov@google.com


This is a recent gcc-4_7-branch regression.

The case builds with trunk (r197936), fails with 4.7 branch (r197941):


struct A
{
    A (int);
};

template < typename >
void Fn ()
{
    const int kCapacity = 0;
    struct Q:A
    {
        Q ():A (kCapacity) { }
    };
    Q q;
}
template void Fn < int >();


$ trunk/bin/g++ -c t.cc && echo ok
ok

$ 4.7/bin/g++ -c t.cc
t.cc: In instantiation of ‘Fn()::Q::Q() [with <template-parameter-1-1> = int]’:
t.cc:14:7:   required from ‘void Fn() [with <template-parameter-1-1> = int]’
t.cc:16:26:   required from here
t.cc:12:26: error: ‘kCapacity’ was not declared in this scope
>From gcc-bugs-return-420222-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Apr 13 16:43:14 2013
Return-Path: <gcc-bugs-return-420222-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20861 invoked by alias); 13 Apr 2013 16:43:14 -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 20841 invoked by uid 48); 13 Apr 2013 16:43:11 -0000
From: "wbrana at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/54078] Bytemark 46% bigger binary with -flto
Date: Sat, 13 Apr 2013 16:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wbrana at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields:
Message-ID: <bug-54078-4-OALZ7WyeIl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-54078-4@http.gcc.gnu.org/bugzilla/>
References: <bug-54078-4@http.gcc.gnu.org/bugzilla/>
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
X-SW-Source: 2013-04/txt/msg01367.txt.bz2
Content-length: 399


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

--- Comment #5 from wbrana <wbrana at gmail dot com> 2013-04-13 16:43:10 UTC ---
branch 4.9

without lto
101462 bytes

with -flto -fwhole-program
157243 bytes - linker bfd
155488 bytes - linker gold

other CFLAGS = -O3 -g0 -march=corei7 -fomit-frame-pointer -funroll-loops
-ffast-math -fno-PIE -fno-exceptions -fno-stack-protector


             reply	other threads:[~2013-04-13 16:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-13 16:06 ppluzhnikov at google dot com [this message]
2013-04-15 10:25 ` [Bug c++/56947] [4.7 Regression] " rguenth at gcc dot gnu.org
2014-05-26 15:44 ` jakub at gcc dot gnu.org
2014-05-27  8:51 ` rguenth at gcc dot gnu.org
2014-05-29 17:55 ` jason at gcc dot gnu.org
2014-05-30 18:56 ` jason at gcc dot gnu.org
2014-05-30 18:58 ` jason at gcc dot gnu.org
2014-07-14 20:40 ` jason at gcc dot gnu.org

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-56947-4@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).