[Bug c++/13549] Problem compiling Boost.Python test

2005-12-18 Thread pinskia at gcc dot gnu dot org
-- pinskia at gcc dot gnu dot org changed: What|Removed |Added Last reconfirmed|2005-09-17 03:51:23 |2005-12-18 20:25:55 date||

[Bug c++/12567] g++ fails to recognize ill-formed-ness of initilaizers

2005-12-18 Thread pinskia at gcc dot gnu dot org
-- pinskia at gcc dot gnu dot org changed: What|Removed |Added Last reconfirmed|2005-09-17 03:38:16 |2005-12-18 20:23:29 date||

[Bug tree-optimization/16876] [3.4/4.0/4.1/4.2 Regression] ICE on testcase with -O3 in gen_lowpart

2005-12-18 Thread steven at gcc dot gnu dot org
--- Comment #10 from steven at gcc dot gnu dot org 2005-12-18 17:15 --- rth assigned this to himself: http://gcc.gnu.org/ml/gcc-bugs/2005-11/msg02843.html A progress report would be nice ;-) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16876 --- You are receiving this mail b

Bug#343898: fix for unreadable error messages in g++ when #define'ing min or max

2005-12-18 Thread Rudi
Package: libstdc++6-4.0-dev Version: 4.0.2-5 Tags: patch Good day, It seems there is an old and thorny issue that has addled my mind for years. It relates to the changing rules in C++ regarding max and min; in early versions, it was perfectly legal to #define max or min as you please, and indeed

[Bug rtl-optimization/21041] [4.0/4.1/4.2 Regression] ICE: output_operand: Cannot decompose address

2005-12-18 Thread uweigand at gcc dot gnu dot org
--- Comment #12 from uweigand at gcc dot gnu dot org 2005-12-18 16:06 --- Subject: Bug 21041 Author: uweigand Date: Sun Dec 18 16:06:55 2005 New Revision: 108760 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=108760 Log: PR rtl-optimization/21041 * reload.c (fin