------- Comment #55 from ubizjak at gmail dot com 2009-05-14 07:51 ------- (In reply to comment #54) > I've started work on the binutils support for this. Work-in-progress patch at > http://sourceware.org/ml/binutils/2009-05/msg00228.html > > Once that's complete, I could deal with the GCC end too. > > What should we do about backward-compatibility? If we attempt to use the new > features with the old toolchain, it won't work, and the linker will issue a > bunch of noisy warnings about the .drectve statements it doesn't understand. > > Should use of the new feature depend on a -m flag, or an assembler/linker > version check of some sort? Or should we just go ahead and let users of old > toolchains get a bunch of warnings? On the same lines, should we still > continue to pad all COMMON symbols to a round multiple of BIGGEST_ALIGNMENT, > or > should we get rid of that when we're using the new feature?
Perhaps you could activate -mno-common if the new feature you are implementing in your binutils patch is not detected by configure? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37216
