public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/57208] Latest chromium compilation fails with enabled LTO
Date: Tue, 25 Jun 2013 11:02:00 -0000	[thread overview]
Message-ID: <bug-57208-4-FkmFoxkKYL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57208-4@http.gcc.gnu.org/bugzilla/>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="UTF-8", Size: 2649 bytes --]

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

--- Comment #29 from Martin Jambor <jamborm at gcc dot gnu.org> ---
(In reply to Martin Liška from comment #28)
> Patch solved the problem for chromium ;) I will test libreoffice tomorrow.

Great, I have submitted the patch to the mailing list then:

http://gcc.gnu.org/ml/gcc-patches/2013-06/msg01422.html
>From gcc-bugs-return-425081-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jun 25 11:06:10 2013
Return-Path: <gcc-bugs-return-425081-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8898 invoked by alias); 25 Jun 2013 11:06:10 -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 8870 invoked by uid 48); 25 Jun 2013 11:06:08 -0000
From: "allan at archlinux dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/57653] filename information discarded when using -imacros
Date: Tue, 25 Jun 2013 11:06: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: 4.8.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: allan at archlinux dot org
X-Bugzilla-Status: WAITING
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: attachments.created
Message-ID: <bug-57653-4-ppa8GHgSSy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-57653-4@http.gcc.gnu.org/bugzilla/>
References: <bug-57653-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: 2013-06/txt/msg01460.txt.bz2
Content-length: 491

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

--- Comment #17 from Allan McRae <allan at archlinux dot org> ---
Created attachment 30359
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id0359&actioníit
gdb log when using -include

When using -include instead of -imacros, the trail is:

LC_ENTER   foo.c
LC_RENAME  <command-line>
LC_ENTER   /usr/include/stdc-predef.h
LC_LEAVE   0x0
LC_ENTER   foo.h
LC_LEAVE   0x0
LC_RENAME  foo.c
LC_LEAVE   0x0

gdb log with -include attached.


  parent reply	other threads:[~2013-06-25 11:02 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-08 12:30 [Bug c++/57208] New: Latest chromium compilation fails with enabled LTO [4.8.1/4.9.0] marxin.liska at gmail dot com
2013-05-08 12:32 ` [Bug c++/57208] " marxin.liska at gmail dot com
2013-06-03 14:50 ` [Bug c++/57208] Latest chromium compilation fails with enabled LTO marxin.liska at gmail dot com
2013-06-03 15:17 ` marxin.liska at gmail dot com
2013-06-05 12:12 ` izamyatin at gmail dot com
2013-06-05 16:26 ` marxin.liska at gmail dot com
2013-06-17 21:46 ` marxin.liska at gmail dot com
2013-06-19 17:03 ` hubicka at gcc dot gnu.org
2013-06-19 17:51 ` ian at airs dot com
2013-06-19 18:04 ` ian at airs dot com
2013-06-19 18:24 ` hubicka at gcc dot gnu.org
2013-06-19 18:27 ` jakub at gcc dot gnu.org
2013-06-19 23:14 ` hubicka at gcc dot gnu.org
2013-06-20  6:26 ` jakub at gcc dot gnu.org
2013-06-20 20:31 ` marxin.liska at gmail dot com
2013-06-21 12:55 ` hubicka at gcc dot gnu.org
2013-06-21 13:01 ` hubicka at gcc dot gnu.org
2013-06-21 13:07 ` marxin.liska at gmail dot com
2013-06-22 21:19 ` marxin.liska at gmail dot com
2013-06-22 21:43 ` hubicka at gcc dot gnu.org
2013-06-22 22:05 ` hubicka at ucw dot cz
2013-06-23 12:20 ` hubicka at ucw dot cz
2013-06-24 10:24 ` jamborm at gcc dot gnu.org
2013-06-24 16:10 ` jamborm at gcc dot gnu.org
2013-06-24 22:25 ` marxin.liska at gmail dot com
2013-06-25 11:02 ` jamborm at gcc dot gnu.org [this message]
2013-07-02 16:42 ` jamborm at gcc dot gnu.org
2013-07-02 16:43 ` jamborm at gcc dot gnu.org
2013-07-17 14:14 ` marxin.liska at gmail dot com
2022-01-01 22:58 ` pinskia 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-57208-4-FkmFoxkKYL@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).