public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/65015] LTO produces randomly ordered debug information Date: Tue, 24 Feb 2015 09:24:00 -0000 [thread overview] Message-ID: <bug-65015-4-q0OlFCYOGp@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65015-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65015 --- Comment #24 from Richard Biener <rguenth at gcc dot gnu.org> --- Author: rguenth Date: Tue Feb 24 09:09:11 2015 New Revision: 220935 URL: https://gcc.gnu.org/viewcvs?rev=220935&root=gcc&view=rev Log: 2015-02-24 Richard Biener <rguenther@suse.de> Backport from mainline 2015-02-11 Richard Biener <rguenther@suse.de> PR lto/65015 * dwarf2out.c (gen_producer_string): Drop -fltrans-output-list and -fresolution. 2015-02-13 Richard Biener <rguenther@suse.de> PR lto/65015 * dwarf2out.c (dwarf2out_finish): Use <artificial> as DW_AT_name for LTO produced CUs. 2015-02-16 Richard Biener <rguenther@suse.de> PR lto/65015 * varasm.c (default_file_start): For LTO produced units emit <artificial> as file directive. 2015-01-17 Jan Kratochvil <jan.kratochvil@redhat.com> * dwarf2out.c (gen_producer_string): Ignore also OPT_fpreprocessed. Modified: branches/gcc-4_9-branch/gcc/ChangeLog branches/gcc-4_9-branch/gcc/dwarf2out.c branches/gcc-4_9-branch/gcc/varasm.c
next prev parent reply other threads:[~2015-02-24 9:09 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-11 10:11 [Bug lto/65015] New: " conchur at web dot de 2015-02-11 11:42 ` [Bug lto/65015] " conchur at web dot de 2015-02-11 12:01 ` rguenth at gcc dot gnu.org 2015-02-11 12:24 ` rguenth at gcc dot gnu.org 2015-02-12 8:42 ` conchur at web dot de 2015-02-12 8:56 ` rguenth at gcc dot gnu.org 2015-02-13 9:36 ` rguenth at gcc dot gnu.org 2015-02-13 9:36 ` rguenth at gcc dot gnu.org 2015-02-13 10:18 ` conchur at web dot de 2015-02-13 11:24 ` rguenth at gcc dot gnu.org 2015-02-13 11:25 ` rguenth at gcc dot gnu.org 2015-02-13 12:45 ` conchur at web dot de 2015-02-13 13:42 ` hjl.tools at gmail dot com 2015-02-13 16:16 ` rguenther at suse dot de 2015-02-13 17:30 ` hjl.tools at gmail dot com 2015-02-13 19:32 ` hjl.tools at gmail dot com 2015-02-13 20:06 ` hjl.tools at gmail dot com 2015-02-14 0:36 ` hjl.tools at gmail dot com 2015-02-16 10:06 ` rguenth at gcc dot gnu.org 2015-02-16 10:08 ` rguenth at gcc dot gnu.org 2015-02-16 14:53 ` rguenth at gcc dot gnu.org 2015-02-16 14:53 ` rguenth at gcc dot gnu.org 2015-02-18 9:26 ` conchur at web dot de 2015-02-24 9:24 ` rguenth at gcc dot gnu.org [this message] 2015-02-24 9:27 ` rguenth at gcc dot gnu.org 2015-02-24 12:15 ` 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-65015-4-q0OlFCYOGp@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: linkBe 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).