public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "daniel.kruegler at googlemail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/67678] Nested class can be re-declared after definition
Date: Sat, 26 Sep 2015 16:56:00 -0000 [thread overview]
Message-ID: <bug-67678-4-vjVwCZpHLG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67678-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67678
Daniel Krügler <daniel.kruegler at googlemail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |daniel.kruegler@googlemail.
| |com
--- Comment #1 from Daniel Krügler <daniel.kruegler at googlemail dot com> ---
Personally I think that allowing this looks like a reasonable extension, but I
agree that using -pedantic this should be diagnosed (which it doesn't yet).
>From gcc-bugs-return-498095-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Sep 26 16:59:10 2015
Return-Path: <gcc-bugs-return-498095-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38401 invoked by alias); 26 Sep 2015 16:59:09 -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 38367 invoked by uid 48); 26 Sep 2015 16:59:06 -0000
From: "daniel.kruegler at googlemail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/67687] [c++0x][constexpr] initialize constexpr member with constexpr constructor
Date: Sat, 26 Sep 2015 16:59: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: critical
X-Bugzilla-Who: daniel.kruegler at googlemail 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: cc
Message-ID: <bug-67687-4-vandihcJJD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-67687-4@http.gcc.gnu.org/bugzilla/>
References: <bug-67687-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-09/txt/msg02073.txt.bz2
Content-length: 499
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67687
Daniel Krügler <daniel.kruegler at googlemail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |daniel.kruegler@googlemail.
| |com
--- Comment #1 from Daniel Krügler <daniel.kruegler at googlemail dot com> ---
Same problem in 6.0 trunk
>From gcc-bugs-return-498096-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Sep 26 17:08:59 2015
Return-Path: <gcc-bugs-return-498096-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52114 invoked by alias); 26 Sep 2015 17:08: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 52086 invoked by uid 48); 26 Sep 2015 17:08:55 -0000
From: "ikozhukhov at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/67725] New: all gcc versions has hardcoded LD path with bootstrap on illumos platform
Date: Sat, 26 Sep 2015 17:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ikozhukhov 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-67725-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/msg02074.txt.bz2
Content-length: 1092
https://gcc.gnu.org/bugzilla/show_bug.cgi?idg725
Bug ID: 67725
Summary: all gcc versions has hardcoded LD path with bootstrap
on illumos platform
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstrap
Assignee: unassigned at gcc dot gnu.org
Reporter: ikozhukhov at gmail dot com
Target Milestone: ---
on autotools i can see we try to use for solaris2* targets :
ld=/usr/ccs/bin/ld
example from gcc-4.8.5/gcc/acinclude.m4:
line 518: gcc_cv_sun_ld_ver=`/usr/ccs/bin/ld -V 2>&1`
it is mistake to use hadrcoded ld path because on illumos we have
ld=/usr/bin/ld and we can specify correct path by:
--without-gnu-ld --with-ld=/usr/bin/ld
but by autotools we will try to identify LD version by hardcoded
/usr/ccs/bin/ld and it is mistake.
have to fix it on all gcc versions, because for DilOS (http://www.dilos.org,
illumos based platform) i have plans remove old /usr/ccs links and it will
failed with gcc bootstrap.
next prev parent reply other threads:[~2015-09-26 16:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 10:04 [Bug c++/67678] New: " redi at gcc dot gnu.org
2015-09-26 16:56 ` daniel.kruegler at googlemail dot com [this message]
2015-09-26 19:24 ` [Bug c++/67678] " redi 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-67678-4-vjVwCZpHLG@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).