On Thu, 14 Feb 2013, Xinliang David Li wrote:
Ok for the google branch -- please provide the patch details in svn
commit message (note that ChangeLog is not needed any more for the
branch).
I don't have commit access (yet). Should I email overse...@gcc.gnu.org as
mentioned at http://gcc.gnu.org/svnwrite.html to get the ball rolling?
On Thu, Feb 14, 2013 at 11:53 AM, Matt Hargett <m...@use.net> wrote:
On Feb 14, 2013, at 10:40 AM, Xinliang David Li <davi...@google.com> wrote:
On Thu, Feb 14, 2013 at 10:18 AM, Matt <m...@use.net> wrote:
The attached patches do two things:
1. Backports a fix from trunk that eliminates bogus warning traces. On my
current codebase which links ~40MB of C++ with LTO, the bogus warning traces
are literally hundreds of lines.
What is the trunk revision?
Richard's original patch was committed to trunk in r195884.
I verified the backport fixed our issue by doing doing a profiledbootstrap
using the bootstrap-lto.mk config with -O3 added. I used the resulting
compiler on the proprietary codebase, C++Benchmark, scummvm, and a few other
open source projects to validate.
2. Our primary development platform is RHEL6.1-based, and the recent
autoconf requirement bump locked us out. I lowered the version, and saw no
difference in ability to configure/bootstrap.
Thanks!
--
tangled strands of DNA explain the way that I behave.
http://www.clock.org/~matt
--
tangled strands of DNA explain the way that I behave.
http://www.clock.org/~matt
