public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jb at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/47938] New: libgfortran symbol version node bumped unnecessarily Date: Tue, 01 Mar 2011 08:44:00 -0000 [thread overview] Message-ID: <bug-47938-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47938 Summary: libgfortran symbol version node bumped unnecessarily Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libfortran AssignedTo: unassigned@gcc.gnu.org ReportedBy: jb@gcc.gnu.org As pointed out by Janus Weil at http://gcc.gnu.org/ml/fortran/2011-02/msg00298.html in 4.5 we have symbol version 1.2. The new symbols for 4.6 should thus be in version node 1.3. However, for some reason 4.6 has added both 1.3 and 1.4, which is unnecessary. We should remove the 1.4 node and merge the symbols into the 1.3 node. OTOH this change would mean that people would need to recompile code compiled with the pre-release 4.6.
next reply other threads:[~2011-03-01 8:44 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-03-01 8:44 jb at gcc dot gnu.org [this message] 2011-03-01 10:10 ` [Bug libfortran/47938] " jakub at gcc dot gnu.org 2011-03-01 11:50 ` jb at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-47938-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).