[Bug libstdc++/49058] [C++0x] Bind no-arguments functor failed using std::bind with -pedantic option.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49058 --- Comment #8 from Jonathan Wakely 2011-05-22 21:23:12 UTC --- It would be wrong though, consider: struct F { int operator(); void operator() const; }; the decltype would detect the return type as 'int' but the function body would return v

[Bug tree-optimization/18767] No vectorization for simple loop

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18767 Uros Bizjak changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

[Bug fortran/49110] Deferred-length character result triggers (false positive) error for pure procedures

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49110 --- Comment #12 from Steve Kargl 2011-05-22 21:30:07 UTC --- On Sun, May 22, 2011 at 08:03:32PM +, jwmwalrus at gmail dot com wrote: > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49110 > > --- Comment #10 from John 2011-05-22 19:36:33 > UT

[Bug libstdc++/49058] [C++0x] Bind no-arguments functor failed using std::bind with -pedantic option.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49058 --- Comment #10 from Jonathan Wakely 2011-05-22 21:29:56 UTC --- For a complete example: struct F { int operator()() const { return 0; } void operator()() const { }; }; int main() { auto const b = std::bind( F() ); int i = b(); // b is

[Bug libstdc++/49058] [C++0x] Bind no-arguments functor failed using std::bind with -pedantic option.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49058 --- Comment #9 from Jonathan Wakely 2011-05-22 21:24:16 UTC --- Duh, sorry, that should have been struct F { int operator()(); void operator()() const; };

[Bug libstdc++/49058] [C++0x] Bind no-arguments functor failed using std::bind with -pedantic option.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49058 --- Comment #11 from Jonathan Wakely 2011-05-22 21:32:05 UTC --- (In reply to comment #10) > For a complete example: > > struct F { > int operator()() const { return 0; } > void operator()() const { }; sigh, I should really take a bit longe

[Bug other/49116] New: GCC fails to bootstrap with -O3 ("may be used uninitialized" errors)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49116 Summary: GCC fails to bootstrap with -O3 ("may be used uninitialized" errors) Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: trivial Priority: P3

[Bug libstdc++/49058] [C++0x] Bind no-arguments functor failed using std::bind with -pedantic option.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49058 --- Comment #12 from Paolo Carlini 2011-05-22 21:47:04 UTC --- Ok, let's make sure to have something similar in the testsuite. And, well, I still believe a tangle of auto return types shouldn't be really necessary in order to solve the problem,

[Bug other/49116] GCC fails to bootstrap with -O3 ("may be used uninitialized" errors)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49116 --- Comment #1 from Dmitry Gorbachev 2011-05-22 21:42:59 UTC --- A patch for another -O3 error is here: .

[Bug libstdc++/49058] [C++0x] Bind no-arguments functor failed using std::bind with -pedantic option.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49058 --- Comment #14 from Paolo Carlini 2011-05-22 22:20:24 UTC --- Sorry, hit return inadvertently. Anyway, the idea would be, instead of just writing: const _Functor writing something like: typename conditional<(sizeof...(_Args) >= 0,

[Bug libstdc++/49058] [C++0x] Bind no-arguments functor failed using std::bind with -pedantic option.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49058 --- Comment #13 from Paolo Carlini 2011-05-22 22:17:10 UTC --- What about creating an artificially dependent context, thus amenable to SFINAE, like: // Call as const template= 0), typename add_const<_Functor>::type, typename add_const<_Funct

[Bug libstdc++/49058] [C++0x] Bind no-arguments functor failed using std::bind with -pedantic option.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49058 --- Comment #15 from Paolo Carlini 2011-05-22 22:30:55 UTC --- This is something which actually passes the testsuite, and the tests here and the new test explained by Jon. Maybe something even more clean along the same lines is possible, but I wo

[Bug fortran/48979] FRACTION und EXPONENT return invalid results for infinity/NaN

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48979 --- Comment #14 from kargl at gcc dot gnu.org 2011-05-22 23:02:01 UTC --- Created attachment 24333 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=24333 patch for simplification

[Bug fortran/48979] FRACTION und EXPONENT return invalid results for infinity/NaN

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48979 --- Comment #15 from kargl at gcc dot gnu.org 2011-05-22 23:03:22 UTC --- (In reply to comment #14) > Created attachment 24333 [details] > patch for simplification I doubt that I'll be able to go beyond this. I'm not clever enough nor fluent enou

[Bug libstdc++/49058] [C++0x] Bind no-arguments functor failed using std::bind with -pedantic option.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49058 --- Comment #16 from Paolo Carlini 2011-05-22 22:52:13 UTC --- With enable_if becomes a tad more concise. /// Index: include/std/functional === --- include/std/func

[Bug libstdc++/49058] [C++0x] Bind no-arguments functor failed using std::bind with -pedantic option.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49058 --- Comment #17 from Jonathan Wakely 2011-05-22 23:09:06 UTC --- nice trick, if that passes the testsuite I'd check it in

[Bug c++/49117] New: 4.5 -> 4.6: user-unfriendly change in "invalid conversion" error message

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49117 Summary: 4.5 -> 4.6: user-unfriendly change in "invalid conversion" error message Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug libstdc++/49058] [C++0x] Bind no-arguments functor failed using std::bind with -pedantic option.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49058 --- Comment #18 from paolo at gcc dot gnu.org 2011-05-23 00:05:29 UTC --- Author: paolo Date: Mon May 23 00:05:24 2011 New Revision: 174048 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=174048 Log: 2011-05-22 Jonathan Wakely * te

[Bug libstdc++/49058] [C++0x] Bind no-arguments functor failed using std::bind with -pedantic option.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49058 --- Comment #20 from Paolo Carlini 2011-05-23 00:10:24 UTC --- Thanks Jon. Thus, library issue fixed in mainline and 4_6-branch. Jason, I think you can safely commit the compiler change in mainline...

[Bug libstdc++/49058] [C++0x] Bind no-arguments functor failed using std::bind with -pedantic option.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49058 Paolo Carlini changed: What|Removed |Added Status|ASSIGNED|NEW AssignedTo|redi at gcc dot gn

[Bug libstdc++/49058] [C++0x] Bind no-arguments functor failed using std::bind with -pedantic option.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49058 --- Comment #19 from paolo at gcc dot gnu.org 2011-05-23 00:09:00 UTC --- Author: paolo Date: Mon May 23 00:08:52 2011 New Revision: 174049 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=174049 Log: 2011-05-22 Jonathan Wakely * te

[Bug c++/49118] New: Endless operator-> chain causes infinite loop

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49118 Summary: Endless operator-> chain causes infinite loop Product: gcc Version: 4.5.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassi

[Bug rtl-optimization/49007] ICE in extract_true_false_edges_from_block at tree-cfg.c:7379

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49007 --- Comment #11 from John David Anglin 2011-05-23 02:39:31 UTC --- It seems to me the following is broken: Once we have found a basic block and a corresponding first insn, we can accurately compute the live status (by starting at a label f

[Bug rtl-optimization/49034] ARM optimizer generating incorrect code (causing bad pointer dereference)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49034 --- Comment #2 from Michael Brown 2011-05-23 06:38:35 UTC --- Based on previous experiences, it'll be at least a couple of weeks to bring up a similarly configured (cross-compiling darwin-x86 -> arm-eabi) FSF toolchain. The command line is (path

<    1   2