public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mliska at suse dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/63409] [5 Regression] FAIL: g++.dg/lto/pr63270 cp_lto_pr63270_0.o-cp_lto_pr63270_1.o link, -flto -O2 -Wno-odr -fno-linker-plugin
Date: Tue, 30 Sep 2014 11:10:00 -0000 [thread overview]
Message-ID: <bug-63409-4-jnjC1ppji3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63409-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63409
Martin Liška <mliska at suse dot cz> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mliska at suse dot cz
--- Comment #2 from Martin Liška <mliska at suse dot cz> ---
Mine. I will prepare the testcase to resolve missing references.
>From gcc-bugs-return-462921-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Sep 30 11:11:34 2014
Return-Path: <gcc-bugs-return-462921-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16971 invoked by alias); 30 Sep 2014 11:11:34 -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 16919 invoked by uid 48); 30 Sep 2014 11:11:30 -0000
From: "mliska at suse dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/35545] tracer pass is run too late
Date: Tue, 30 Sep 2014 11:11: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.4.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: mliska at suse dot cz
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-35545-4-Bcff9kksn3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-35545-4@http.gcc.gnu.org/bugzilla/>
References: <bug-35545-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: 2014-09/txt/msg02755.txt.bz2
Content-length: 198
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35545
--- Comment #24 from Martin Liška <mliska at suse dot cz> ---
Hello Honza. I've been working on SPEC numbers, I will send it this evening.
>From gcc-bugs-return-462922-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Sep 30 11:38:41 2014
Return-Path: <gcc-bugs-return-462922-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29566 invoked by alias); 30 Sep 2014 11:38: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 29548 invoked by uid 48); 30 Sep 2014 11:38:35 -0000
From: "tomalk at mathematik dot uni-freiburg.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/63414] New: template parse error using < operator
Date: Tue, 30 Sep 2014 11:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tomalk at mathematik dot uni-freiburg.de
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
Message-ID: <bug-63414-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-09/txt/msg02756.txt.bz2
Content-length: 406
https://gcc.gnu.org/bugzilla/show_bug.cgi?idc414
Bug ID: 63414
Summary: template parse error using < operator
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: tomalk at mathematik dot uni-freiburg.de
next prev parent reply other threads:[~2014-09-30 11:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 15:58 [Bug lto/63409] New: " ubizjak at gmail dot com
2014-09-30 10:18 ` [Bug lto/63409] " rguenth at gcc dot gnu.org
2014-09-30 10:46 ` dominiq at lps dot ens.fr
2014-09-30 11:10 ` mliska at suse dot cz [this message]
2014-10-03 13:33 ` ubizjak at gmail dot com
2014-10-06 14:33 ` ro at gcc dot gnu.org
2014-10-06 16:18 ` mliska at suse dot cz
2014-10-07 6:45 ` ubizjak at gmail dot com
2014-10-07 8:28 ` mliska at suse dot cz
2014-10-07 11:01 ` rguenth 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-63409-4-jnjC1ppji3@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).