Gary Funck <g...@intrepid.com> writes: > We recently ran into this 'as' bug running > tests with the GCC (4.5 pre-cursor) "trunk" compiler > on an x86_64 target running Ubuntu 8.04: > http://sourceware.org/bugzilla/show_bug.cgi?id=10255 > (the bug was marked fixed in June 2009). > > The issue was noted in this GCC PR: > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40332 > > Since GCC 4.5 isn't out yet, I'm wondering what is > the policy, or general rule that is followed with > respect to a new version of GCC being dependent > upon a particular version of binutils, or some > important library? > > And, would it make sense in this case to have > a GCC test case that exercises this 'as' bug to > be able to detect that either the bug is there in > the version of 'as' that is being used to build > and test GCC, or that a regression occurred?
I think it would be troubling if a gcc release required a very new binutils release on a popular platform like x86_64. I think we should work hard to avoid that. If I understand this issue correctly, it should be possible to modify the configure test for gcc_cv_as_cfi_directive to avoid the problem when using an older binutils. If that is true, then I think we should push PR 40332 up to P1 until gcc works correctly with binutils older than 2.20. Ian
