------- Comment #17 from hjl dot tools at gmail dot com 2008-07-01 04:07 ------- (In reply to comment #16) > So the question is whether we should break programs compiled by 4.3.0 and > 4.3.1 > (acknowledging that there may not be any actual programs that break) in order > to use consistent version numbers? > > > 1. What version should x86-64 TF symbols use? > > What is the argument for changing them now that they have been released?
Because GCC_4.3.0 is the first version which implements them? > > > 2. What version should ia32 TF symbols use? > > If I understand correctly, these have not been released, so it seems that they > should be GCC_4.4.0. > > > 3. Should ALL x86-64 TF symbols have the same version? > > I don't see why this is necessary. > If people think we don't need to set the correct version on those TF symbols, could someone please close this bug as WONTFIX? I need a closure to update my ia32 quad patch since my patch uses a single libgcc-glibc.ver for x86, which currently defines all x86-64 TF symbols with version GCC_4.3.0. Thanks. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36669
