public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin.liska at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/56312] Firefox 20.0a1 compilation with enabled LTO fails
Date: Sat, 23 Mar 2013 23:42:00 -0000 [thread overview]
Message-ID: <bug-56312-4-xxmu21ORz4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56312-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56312
--- Comment #7 from Martin Liška <marxin.liska at gmail dot com> 2013-03-23 23:42:28 UTC ---
The problem was caused by bad usage of gcc-ar and gcc-runlib that were actually
not used.
>From gcc-bugs-return-418242-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Mar 23 23:43:43 2013
Return-Path: <gcc-bugs-return-418242-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24331 invoked by alias); 23 Mar 2013 23:43:43 -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 24300 invoked by uid 48); 23 Mar 2013 23:43:36 -0000
From: "marxin.liska at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/56312] Firefox 20.0a1 compilation with enabled LTO fails
Date: Sat, 23 Mar 2013 23:43: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-Keywords: lto
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin.liska at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields: Status Resolution
Message-ID: <bug-56312-4-QEU6jXmSrS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-56312-4@http.gcc.gnu.org/bugzilla/>
References: <bug-56312-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"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-SW-Source: 2013-03/txt/msg01683.txt.bz2
Content-length: 475
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56312
Martin Liška <marxin.liska at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |INVALID
--- Comment #8 from Martin Liška <marxin.liska at gmail dot com> 2013-03-23 23:43:36 UTC ---
Invalid bug.
>From gcc-bugs-return-418243-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Mar 24 07:06:50 2013
Return-Path: <gcc-bugs-return-418243-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12092 invoked by alias); 24 Mar 2013 07:06:50 -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 12030 invoked by uid 48); 24 Mar 2013 07:06:42 -0000
From: "gcc@Denis-Excoffier.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/56258] Please upgrade doc/*.texi to the latest texinfo package(s)
Date: Sun, 24 Mar 2013 07:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gcc@Denis-Excoffier.org
X-Bugzilla-Status: RESOLVED
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-56258-4-vX53yheL1U@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-56258-4@http.gcc.gnu.org/bugzilla/>
References: <bug-56258-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-03/txt/msg01684.txt.bz2
Content-length: 203
http://gcc.gnu.org/bugzilla/show_bug.cgi?idV258
--- Comment #16 from Denis Excoffier <gcc@Denis-Excoffier.org> 2013-03-24 07:06:40 UTC ---
Bootstrap of gcc-4.7-20130323 works perfectly. Thanks.
prev parent reply other threads:[~2013-03-23 23:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 22:32 [Bug c++/56312] New: " marxin.liska at gmail dot com
2013-02-28 18:31 ` [Bug c++/56312] " marxin.liska at gmail dot com
2013-03-01 16:32 ` hubicka at gcc dot gnu.org
2013-03-02 17:37 ` marxin.liska at gmail dot com
2013-03-02 17:50 ` hubicka at gcc dot gnu.org
2013-03-12 13:04 ` hubicka at gcc dot gnu.org
2013-03-12 13:31 ` marxin.liska at gmail dot com
2013-03-23 23:42 ` marxin.liska 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-56312-4-xxmu21ORz4@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).