[Bug target/43764] -mrelax-pic-calls fails with complex types

2012-12-21 Thread sje at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43764 Steve Ellcey changed: What|Removed |Added Status|ASSIGNED|RESOLVED CC|

[Bug c++/55783] New: Warnings instead of compiler errors for narrowing conversions within list-initializations

2012-12-21 Thread david at stellarscience dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55783 Bug #: 55783 Summary: Warnings instead of compiler errors for narrowing conversions within list-initializations Classification: Unclassified Product: gcc Version: 4.7.2

[Bug c++/55783] Warnings instead of compiler errors for narrowing conversions within list-initializations

2012-12-21 Thread pinskia at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55783 --- Comment #1 from Andrew Pinski 2012-12-22 00:06:50 UTC --- "With -std=c++11, -Wno-narrowing suppresses the diagnostic required by the standard. Note that this does not affect the meaning of well-formed code; narrowing conversions are st

[Bug c++/55783] Warnings instead of compiler errors for narrowing conversions within list-initializations

2012-12-21 Thread david at stellarscience dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55783 --- Comment #2 from David Sankel 2012-12-22 00:13:33 UTC --- >From what I understand, the standard requires the compiler to reject the program, not to accept it with a warning.

[Bug c++/55783] Warnings instead of compiler errors for narrowing conversions within list-initializations

2012-12-21 Thread pinskia at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55783 --- Comment #3 from Andrew Pinski 2012-12-22 00:15:04 UTC --- use -Werror=Wnarrowing then

[Bug c++/55783] Warnings instead of compiler errors for narrowing conversions within list-initializations

2012-12-21 Thread redi at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55783 Jonathan Wakely changed: What|Removed |Added Severity|major |normal --- Comment #4 from Jo

[Bug c++/55783] Warnings instead of compiler errors for narrowing conversions within list-initializations

2012-12-21 Thread redi at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55783 --- Comment #5 from Jonathan Wakely 2012-12-22 00:27:51 UTC --- (In reply to comment #4) > The standard only requires that "a conforming implementation shall issue at > least one diagnostic message" (This is from 1.4 [intro.compliance]

[Bug c++/55783] Warnings instead of compiler errors for narrowing conversions within list-initializations

2012-12-21 Thread david at stellarscience dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55783 --- Comment #6 from David Sankel 2012-12-22 00:33:44 UTC --- I suppose which gnu extensions are, by default, enabled in the -std=c++11 mode is up for debate (one which I have no interest in). However, this program still compiles with "-pedantic"

[Bug c++/55783] Warnings instead of compiler errors for narrowing conversions within list-initializations

2012-12-21 Thread david at stellarscience dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55783 --- Comment #7 from David Sankel 2012-12-22 00:42:35 UTC --- I just realized my above comment doesn't make much sense regarding the standard. Please disregard. On the other hand it seems like -pedantic should reject this program, no?

[Bug c++/55783] Warnings instead of compiler errors for narrowing conversions within list-initializations

2012-12-21 Thread redi at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55783 Jonathan Wakely changed: What|Removed |Added Keywords||diagnostic --- Comment #8 fro

[Bug bootstrap/55784] New: [4.8 regression] declaration of C function 'const char* strsignal(int)' conflicts with /usr/include/string.h:112: error: previous declaration

2012-12-21 Thread gerald at pfeifer dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55784 Bug #: 55784 Summary: [4.8 regression] declaration of C function 'const char* strsignal(int)' conflicts with /usr/include/string.h:112: error: previous declaration Classifi

[Bug bootstrap/55784] [4.8 regression] declaration of C function 'const char* strsignal(int)' conflicts with /usr/include/string.h:112: error: previous declaration

2012-12-21 Thread pinskia at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55784 Andrew Pinski changed: What|Removed |Added Keywords||build Status|UNCONFI

[Bug c++/55785] New: gcc4.5.2 incorrect line # of caller for destructor

2012-12-21 Thread chihin.ko at oracle dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55785 Bug #: 55785 Summary: gcc4.5.2 incorrect line # of caller for destructor Classification: Unclassified Product: gcc Version: 4.5.2 Status: UNCONFIRMED Severity: normal

[Bug c++/55785] gcc4.5.2 incorrect line # of caller for destructor

2012-12-21 Thread pinskia at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55785 Andrew Pinski changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|

[Bug debug/49951] [4.5/4.6/4.7 Regression] Debug stepping behavior regarding g++ Class destructor has changed for the worse starting at gcc 4.5.0

2012-12-21 Thread pinskia at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49951 Andrew Pinski changed: What|Removed |Added CC||chihin.ko at oracle dot com ---

[Bug c++/55773] C++ class object destructors are not called which a static class object in destructor function in a shared library after dlclose is called.

2012-12-21 Thread liuhc001 at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55773 --- Comment #2 from liuhc001 at gmail dot com 2012-12-22 07:44:48 UTC --- (In reply to comment #1) > GCC 4.1.2 is very old and has not been maintained for years, please try to > reproduce this with a current version of GCC. I try it at 4.

<    1   2