[Bug lto/53604] ld reports errors using lto after upgrading from gcc-4.6.2 to gcc-4.7.0

2012-09-06 Thread paul.scruby at ghco dot co.uk
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53604 --- Comment #12 from Paul Scruby 2012-09-06 13:03:17 UTC --- I just tried Matt Hargett's patch from Bug53572 with gcc4.7.1 and it still has not fixed the problem we're having. I'll continue test these issues in our codebase with new versions of

[Bug lto/53604] ld reports errors using lto after upgrading from gcc-4.6.2 to gcc-4.7.0

2012-06-14 Thread paul.scruby at ghco dot co.uk
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53604 --- Comment #11 from Paul Scruby 2012-06-14 11:46:32 UTC --- I've written half a dozen test harnesses this morning to tried to recreate this bug unsuccessfully. My team writes very low-latency code so they do quite a lot of 'abusive' (but legal)

[Bug lto/53604] ld reports errors using lto after upgrading from gcc-4.6.2 to gcc-4.7.0

2012-06-14 Thread paul.scruby at ghco dot co.uk
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53604 --- Comment #10 from Paul Scruby 2012-06-14 08:16:28 UTC --- I released that I needed to add Yuri's patch to gcc-4.7.1.RC-20120606 as it had not made it into the trunk. However, this still made no difference and I still had the same linking prob

[Bug lto/53604] ld reports errors using lto after upgrading from gcc-4.6.2 to gcc-4.7.0

2012-06-13 Thread paul.scruby at ghco dot co.uk
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53604 --- Comment #9 from Paul Scruby 2012-06-13 16:44:12 UTC --- Unfortunately I still have this linking issue with gcc-4.7.1-RC-20120606 and binutils-2.22 so I don't think it's a dup for PR 53572. I'll try to make a standalone project tomorrow which

[Bug lto/53604] ld reports errors using lto after upgrading from gcc-4.6.2 to gcc-4.7.0

2012-06-13 Thread paul.scruby at ghco dot co.uk
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53604 --- Comment #8 from Paul Scruby 2012-06-13 14:34:38 UTC --- Cheers Jon, I'll try this afternoon...

[Bug lto/53604] ld reports errors using lto after upgrading from gcc-4.6.2 to gcc-4.7.0

2012-06-13 Thread paul.scruby at ghco dot co.uk
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53604 Paul Scruby changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|DUPLICATE

[Bug lto/53604] ld reports errors using lto after upgrading from gcc-4.6.2 to gcc-4.7.0

2012-06-07 Thread paul.scruby at ghco dot co.uk
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53604 --- Comment #2 from Paul Scruby 2012-06-07 17:14:13 UTC --- The 4.7.0 code is different so the patch didn't work: 'struct varpool_node' has no member named 'symbol' I'm not familiar with the gcc internals so I'm not sure what I need to add to

[Bug lto/53604] New: ld reports errors using lto after upgrading from gcc-4.6.2 to gcc-4.7.0

2012-06-07 Thread paul.scruby at ghco dot co.uk
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53604 Bug #: 53604 Summary: ld reports errors using lto after upgrading from gcc-4.6.2 to gcc-4.7.0 Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFI