From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16302 invoked by alias); 1 Mar 2011 11:50:50 -0000 Received: (qmail 16293 invoked by uid 22791); 1 Mar 2011 11:50:49 -0000 X-SWARE-Spam-Status: No, hits=-2.8 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00,TW_BG X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 01 Mar 2011 11:50:45 +0000 From: "jb at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/47938] libgfortran symbol version node bumped unnecessarily X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libfortran X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jb at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Status Resolution Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Date: Tue, 01 Mar 2011 11:50:00 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2011-03/txt/msg00053.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47938 Janne Blomqvist changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |WONTFIX --- Comment #2 from Janne Blomqvist 2011-03-01 11:50:33 UTC --- Yes, I'm leaning that way as well. FWIW, from looking at commit logs and old mails, it seems 1.4 was added due to some confusion with symbol versioning and ABI compatibility. In any case, closing as wontfix. If anyone comes up with a convincing argument why this should be fixed, please reopen (and, be quick about it as 4.6 is going to be released quite soon I think, and after that we certainly can't remove a symbol node in a released branch).