public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/64025] [5 Regression] Several testsuite execution failures with -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects Date: Thu, 27 Nov 2014 11:02:00 -0000 [thread overview] Message-ID: <bug-64025-4-WH26jkaRXu@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64025-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64025 --- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Author: jakub Date: Thu Nov 27 11:02:02 2014 New Revision: 218119 URL: https://gcc.gnu.org/viewcvs?rev=218119&root=gcc&view=rev Log: PR lto/64025 * alias.c (find_base_term): Use std::swap. Prefer tmp2 if it is CONSTANT_P other than CONST_INT. Modified: trunk/gcc/ChangeLog trunk/gcc/alias.c
prev parent reply other threads:[~2014-11-27 11:02 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-11-22 12:12 [Bug lto/64025] New: " ubizjak at gmail dot com 2014-11-24 11:26 ` [Bug lto/64025] [5 Regression] " rguenth at gcc dot gnu.org 2014-11-24 14:52 ` hjl.tools at gmail dot com 2014-11-24 18:41 ` jakub at gcc dot gnu.org 2014-11-24 18:48 ` jakub at gcc dot gnu.org 2014-11-24 19:00 ` ubizjak at gmail dot com 2014-11-27 11:02 ` jakub at gcc dot gnu.org [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-64025-4-WH26jkaRXu@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).