[Bug 915018] Re: gcc 4.7.0 fixes a bug that Crypto++ 5.6.1 relies on
Launchpad has imported 4 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=773443. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2012-01-11T20:45:06+00:00 Zooko wrote: Description of problem: gcc-4.7.0 fixes a bug that various packages rely on Version-Release number of selected component (if applicable): 4.7.0 How reproducible: 100% deterministic. Steps to Reproduce: 1. Try to build a package such as Crypto++ v5.6.1 with a pre-release of gcc 4.7.0. 2. 3. Actual results: Compile failure. Expected results: Compile success. Additional info: As reported by Jakub Jellinek: http://lists.fedoraproject.org/pipermail/devel/2011-December/160723.html As tracked on launchpad: https://bugs.launchpad.net/gcc/+bug/915018, which has links to the issue trackers for Crypto++ and pycryptopp. Reply at: https://bugs.launchpad.net/ubuntu/+source/libcrypto++/+bug/915018/comments/12 On 2012-01-11T22:51:37+00:00 Jakub wrote: Why are you filing it against gcc? It is completely intentional. Just fix your package(s). Reply at: https://bugs.launchpad.net/ubuntu/+source/libcrypto++/+bug/915018/comments/13 On 2012-01-11T23:48:09+00:00 Zooko wrote: I didn't mean to denote that it was a (current) bug in gcc. I just meant to let myself and others track the fact that the gcc 4.7.0 release (and pre-releases) interact with this bug, and I meant to link to the original gcc ticket: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24163 I guess ideally I would mark this ticket as applying to the list of packages that you posted to the mailing list, but I don't know if that's possible and if it is I'm not going to take the time to do it manually. ;-) Reply at: https://bugs.launchpad.net/ubuntu/+source/libcrypto++/+bug/915018/comments/14 On 2012-01-11T23:52:57+00:00 Zooko wrote: P.S. I guess I was thinking of "the package of gcc that is shipped in Fedora" as being one of the subjects of this ticket, more than "gcc itself". I figured it might help other people to understand that if they are seeing these errors, it is the combination of gcc 4.7.0 pre-release and their other packages that results in the errors. But again, I didn't intend to say that the errors were caused by gcc having a bug. Also, of course, Crypto++ and quite a few other packages are also the subjects of this issue. The launchpad ticket -- https://bugs.launchpad.net/gcc/+bug/915018 -- has links to relevant tickets in various issue trackers. For my own future reference: 1. Is there a way to express in bugzilla.redhat.com that an issue affects a package of software $X version $Y within Fedora release $Z? Ideally I would have said "This is an issue you may have if you're using the 4.7.0 pre-release distributed in Fedora Rawhide.". Is there a way to express that in the bugzilla db? 2. Is there a way to denote "This is an issue that affects $X or that the presence of $X can trigger, but is not a bug in $X?". Thanks! Reply at: https://bugs.launchpad.net/ubuntu/+source/libcrypto++/+bug/915018/comments/15 ** Changed in: libcrypto++ (Fedora) Status: Unknown => Invalid ** Changed in: libcrypto++ (Fedora) Importance: Unknown => Undecided -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/915018 Title: gcc 4.7.0 fixes a bug that Crypto++ 5.6.1 relies on To manage notifications about this bug go to: https://bugs.launchpad.net/cryptopp/+bug/915018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 915018] Re: gcc 4.7.0 fixes a bug that Crypto++ 5.6.1 relies on
** Changed in: cryptopp Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/915018 Title: gcc 4.7.0 fixes a bug that Crypto++ 5.6.1 relies on To manage notifications about this bug go to: https://bugs.launchpad.net/cryptopp/+bug/915018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 915018] Re: gcc 4.7.0 fixes a bug that Crypto++ 5.6.1 relies on
** Changed in: libcrypto++ (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/915018 Title: gcc 4.7.0 fixes a bug that Crypto++ 5.6.1 relies on To manage notifications about this bug go to: https://bugs.launchpad.net/cryptopp/+bug/915018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 915018] Re: gcc 4.7.0 fixes a bug that Crypto++ 5.6.1 relies on
The hyperlink to the issue in the Fedora issue tracker is https://bugzilla.redhat.com/show_bug.cgi?id=773443 . (This is a test of LaunchPad. If you, oh noble LaunchPad, update this ticket to have a hyperlink to that ticket in the table of other projects/distros that this Affects, at the top, then you win! Except if, in doing so, you blow away the invalid setting in the Status column and the Fedora row, then you lose! See https://bugs.launchpad.net/launchpad/+bug/931582 .) ** Package changed: gcc-4.7 (Fedora) = fedora ** Changed in: fedora Importance: Unknown = Undecided ** Changed in: fedora Status: Unknown = New ** Changed in: fedora Remote watch: Red Hat Bugzilla #773443 = None ** Changed in: fedora Status: New = Invalid ** Bug watch added: Red Hat Bugzilla #773443 https://bugzilla.redhat.com/show_bug.cgi?id=773443 ** Changed in: fedora Importance: Undecided = Unknown ** Changed in: fedora Status: Invalid = Unknown ** Changed in: fedora Remote watch: None = Red Hat Bugzilla #773443 ** Changed in: fedora Importance: Unknown = Undecided ** Changed in: fedora Status: Unknown = New ** Changed in: fedora Remote watch: Red Hat Bugzilla #773443 = None ** Changed in: fedora Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/915018 Title: gcc 4.7.0 fixes a bug that Crypto++ 5.6.1 relies on To manage notifications about this bug go to: https://bugs.launchpad.net/cryptopp/+bug/915018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 915018] Re: gcc 4.7.0 fixes a bug that Crypto++ 5.6.1 relies on
** Changed in: pycryptopp Status: Unknown = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/915018 Title: gcc 4.7.0 fixes a bug that Crypto++ 5.6.1 relies on To manage notifications about this bug go to: https://bugs.launchpad.net/cryptopp/+bug/915018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 915018] Re: gcc 4.7.0 fixes a bug that Crypto++ 5.6.1 relies on
** Bug watch added: Red Hat Bugzilla #773443 https://bugzilla.redhat.com/show_bug.cgi?id=773443 ** Also affects: libcrypto++ (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=773443 Importance: Unknown Status: Unknown ** Also affects: gcc-4.7 (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=773443 Importance: Unknown Status: Unknown ** Also affects: pycryptopp via http://tahoe-lafs.org/trac/pycryptopp/ticket/78 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/915018 Title: gcc 4.7.0 fixes a bug that Crypto++ 5.6.1 relies on To manage notifications about this bug go to: https://bugs.launchpad.net/cryptopp/+bug/915018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 915018] Re: gcc 4.7.0 fixes a bug that Crypto++ 5.6.1 relies on
Launchpad has imported 11 comments from the remote bug at
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24163.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
On 2005-10-01T16:24:48+00:00 Jwakely-gcc wrote:
(I first posted this code to PR5660 but it's apparently a separate
issue)
template typename T
struct A
{
typedef T Type;
void f(Type) {}
};
template typename T
struct B : AT
{
typedef typename AT::Type Type;
void ff(Type t) { f(t); } // XXX
};
template struct Bint;
This should fail to compile, according to 14.6.2/3, but 3.4 - 4.1 (and probably
earlier) accept it.
If A::f and the call to it are changed to take no arguments (so that f is not a
dependent name) then it fails, so it is apparently only at instantiation that
the base class scope is examined.
Reply at: https://bugs.launchpad.net/cryptopp/+bug/915018/comments/0
On 2005-10-01T16:28:10+00:00 Pinskia wrote:
Confirmed.
Reply at: https://bugs.launchpad.net/cryptopp/+bug/915018/comments/1
On 2005-10-01T16:48:44+00:00 Jwakely-gcc wrote:
Adding ... in template to end of title.
Reply at: https://bugs.launchpad.net/cryptopp/+bug/915018/comments/2
On 2009-12-05T00:01:56+00:00 Pinskia wrote:
*** Bug 42291 has been marked as a duplicate of this bug. ***
Reply at: https://bugs.launchpad.net/cryptopp/+bug/915018/comments/3
On 2009-12-05T00:03:48+00:00 Pinskia wrote:
This is related to PR 15272 where we look at both dependent and non
dependent base classes when only non dependent should be looked at.
Actually I think this is a dup of that bug but I will leave it to a C++
expert.
Reply at: https://bugs.launchpad.net/cryptopp/+bug/915018/comments/4
On 2010-11-30T19:14:37+00:00 Pinskia wrote:
*** Bug 43282 has been marked as a duplicate of this bug. ***
Reply at: https://bugs.launchpad.net/cryptopp/+bug/915018/comments/5
On 2011-02-02T11:57:52+00:00 Redi wrote:
*** Bug 47585 has been marked as a duplicate of this bug. ***
Reply at: https://bugs.launchpad.net/cryptopp/+bug/915018/comments/6
On 2011-05-20T18:01:27+00:00 Jason-gcc wrote:
Author: jason
Date: Fri May 20 18:01:22 2011
New Revision: 173965
URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=173965
Log:
PR c++/24163
PR c++/29131
gcc/cp/
* pt.c (tsubst_copy_and_build) [CALL_EXPR]: Avoid repeating
unqualified lookup.
* semantics.c (perform_koenig_lookup): Add complain parm.
* cp-tree.h: Adjust.
* parser.c (cp_parser_postfix_expression): Adjust.
(cp_parser_perform_range_for_lookup): Adjust.
libstdc++-v3/
* include/ext/pb_ds/assoc_container.hpp: Explicitly qualify calls to
functions from dependent bases.
* include/ext/pb_ds/detail/rb_tree_map_/erase_fn_imps.hpp: Likewise.
* include/ext/pb_ds/detail/rb_tree_map_/
split_join_fn_imps.hpp: Likewise.
* include/ext/pb_ds/detail/splay_tree_/erase_fn_imps.hpp: Likewise.
* include/ext/pb_ds/detail/splay_tree_/insert_fn_imps.hpp: Likewise.
* include/ext/pb_ds/detail/splay_tree_/splay_fn_imps.hpp: Likewise.
* include/ext/pb_ds/detail/splay_tree_/
split_join_fn_imps.hpp: Likewise.
* include/ext/pb_ds/detail/tree_policy/
order_statistics_imp.hpp: Likewise.
* include/ext/pb_ds/detail/trie_policy/
prefix_search_node_update_imp.hpp: Likewise.
* include/ext/rc_string_base.h: Likewise.
* include/ext/rope: Likewise.
* include/ext/ropeimpl.h: Likewise.
* testsuite/util/exception/safety.h: Likewise.
* testsuite/util/native_type/native_priority_queue.hpp: Likewise.
* testsuite/util/testsuite_io.h: Likewise.
* include/std/functional: Declare mem_fn earlier.
* include/tr1/functional: Likewise.
* include/tr1/exp_integral.tcc: Declare __expint_E1 earlier.
Added:
trunk/gcc/testsuite/g++.dg/template/koenig9.C
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/cp-tree.h
trunk/gcc/cp/parser.c
trunk/gcc/cp/pt.c
trunk/gcc/cp/semantics.c
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/g++.dg/opt/pr47615.C
trunk/gcc/testsuite/g++.dg/overload/defarg1.C
