[Bug rtl-optimization/24683] [3.4/4.0/4.1 Regression] ICE in in extract_insn, at recog.c:2084

2005-11-07 Thread mueller at kde dot org
--- Comment #21 from mueller at kde dot org 2005-11-07 18:45 --- its an error in the testcase, the original code initializes i: if((j + len) > 63) { 562 memcpy(&context->buffer[j], data, (i = 64-j)); 563 transfo

[Bug c++/14024] g++ isn't reporting aliasing warnings

2005-12-07 Thread mueller at kde dot org
--- Comment #8 from mueller at kde dot org 2005-12-07 16:33 --- that comparison isn't quite fair. strict aliasing is an optimisation that breaks code when compiled with a newer version of gcc, and there is lots of code to fix because of that. Sure, you can fix it by reading th

[Bug c/25509] New: can't voidify __attribute__((warn_unused_result))

2005-12-20 Thread mueller at kde dot org
rity: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: mueller at kde dot org GCC host triplet: i686-suse-linux http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25509

[Bug c/25509] can't voidify __attribute__((warn_unused_result))

2005-12-20 Thread mueller at kde dot org
--- Comment #2 from mueller at kde dot org 2005-12-21 00:07 --- background: glibc 2.3 CVS attributes "fwrite" and "write" with it, and it causes a lot (in the hundreds/thousands) of false positives for bigger software projects, because while it is indeed the case

[Bug c/25509] can't voidify __attribute__((warn_unused_result))

2005-12-20 Thread mueller at kde dot org
--- Comment #4 from mueller at kde dot org 2005-12-21 03:35 --- Care to explain how it is a glibc bug? its not documented that there shouldn't be a way to suppress the warning. I agree glibc is overly paranoid and pedantic, but that doesn't make it less of a gcc issue. --

[Bug c/25509] can't voidify __attribute__((warn_unused_result))

2005-12-20 Thread mueller at kde dot org
--- Comment #7 from mueller at kde dot org 2005-12-21 04:02 --- ok, lets assume that you meant with "can not be ignored" actually "must not be ignored". now thats where the definitions in RFC2119 kick in: 2. MUST NOT This phrase, or the phrase "

[Bug c/25509] can't voidify __attribute__((warn_unused_result))

2005-12-20 Thread mueller at kde dot org
--- Comment #8 from mueller at kde dot org 2005-12-21 04:17 --- > ok, lets assume that you meant with "can not be ignored" actually "must not > > be ignored". now thats where the definitions in RFC2119 kick in: Hmm, that wasn't meant so harsh tha

[Bug c/25509] can't voidify __attribute__((warn_unused_result))

2005-12-21 Thread mueller at kde dot org
--- Comment #13 from mueller at kde dot org 2005-12-21 14:07 --- ok, then, lets see if we can get this fixed in glibc. -- mueller at kde dot org changed: What|Removed |Added

[Bug c++/5520] Add a warning to detect empty body of if statements (like in the C frontend)

2006-01-05 Thread mueller at kde dot org
--- Comment #5 from mueller at kde dot org 2006-01-05 10:19 --- http://gcc.gnu.org/ml/gcc-patches/2005-12/msg01627.html -- mueller at kde dot org changed: What|Removed |Added

[Bug c++/19773] warning for misplaced semicolon is C-only

2006-01-05 Thread mueller at kde dot org
--- Comment #2 from mueller at kde dot org 2006-01-05 10:20 --- please resolve this as duplicate for bug 5520 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19773

[Bug c++/5520] Add a warning to detect empty body of if statements (like in the C frontend)

2006-01-08 Thread mueller at kde dot org
--- Comment #8 from mueller at kde dot org 2006-01-08 21:59 --- Created an attachment (id=10596) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=10596&action=view) updated patch I agree, that makes it much more readable. updated accordingly and rediffed against curren

[Bug c++/25855] New: template specialisation not always found

2006-01-19 Thread mueller at kde dot org
igned at gcc dot gnu dot org ReportedBy: mueller at kde dot org GCC host triplet: i686-unknown-linux http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25855

[Bug c++/25855] template specialisation not always found

2006-01-19 Thread mueller at kde dot org
--- Comment #1 from mueller at kde dot org 2006-01-19 11:12 --- Created an attachment (id=10674) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=10674&action=view) testcase -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25855

[Bug c++/25855] template specialisation not always found

2006-01-19 Thread mueller at kde dot org
--- Comment #2 from mueller at kde dot org 2006-01-19 11:13 --- attaching testcase inline for better bugzilla queries: #ifdef BREAK templatebool qCompare(const T *t1, const T *t2); templatebool qCompare(T *t1, T *t2); #else template

[Bug c++/19317] [4.0 Regression] removing a temporary return value when we cannot

2005-02-15 Thread mueller at kde dot org
--- Additional Comments From mueller at kde dot org 2005-02-16 02:02 --- bootstrap failure is fixed, and 16405 works too, but this testcase still fails. -- What|Removed |Added

[Bug c++/19317] [4.0/4.1 Regression] removing a temporary return value when we cannot

2005-03-17 Thread mueller at kde dot org
--- Additional Comments From mueller at kde dot org 2005-03-17 17:33 --- thats the same issue like the konqueror crash which I couldn't find a workaround for in gcc either. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19317

[Bug c++/20562] New: no unused warning for static arrays

2005-03-19 Thread mueller at kde dot org
0 Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: mueller at kde dot org CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20562

[Bug c/20562] no unused warning for static arrays

2005-03-19 Thread mueller at kde dot org
--- Additional Comments From mueller at kde dot org 2005-03-19 23:32 --- whoops, wrong frontend. -- What|Removed |Added Status|RESOLVED

[Bug c/20562] no unused warning for static arrays

2005-03-20 Thread mueller at kde dot org
--- Additional Comments From mueller at kde dot org 2005-03-20 23:22 --- this is where __attribute__((unused)) kicks in.. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20562

[Bug libstdc++/19265] problem with _S_destroy_thread_key when using dynamic libraries

2005-03-24 Thread mueller at kde dot org
-- What|Removed |Added CC||mueller at kde dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19265

[Bug c++/20949] [4.0/4.1 Regression] misscompilation of konqueror, artsd, STLport, libstdc++, ...

2005-04-12 Thread mueller at kde dot org
-- What|Removed |Added CC||mueller at kde dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20949

[Bug c++/19317] [4.1 Regression] removing a temporary return value when we cannot

2005-04-12 Thread mueller at kde dot org
--- Additional Comments From mueller at kde dot org 2005-04-12 10:27 --- there are two more critical miscompilations in branch, popping up 12 and 10 days ago. I'm currently trying to deduce a testcase, but maybe that information already is sufficient to narrow down the f

[Bug c++/19317] [4.1 Regression] removing a temporary return value when we cannot

2005-04-12 Thread mueller at kde dot org
--- Additional Comments From mueller at kde dot org 2005-04-13 01:10 --- the konqueror startup crash is fixed by: @@ -3716,7 +3716,7 @@ void KonqMainWindow::initActions() m_paActivateNextTab = new KAction( i18n( "Activate Next Tab" ), "tab_next", QApplic

[Bug c++/19317] [4.1 Regression] removing a temporary return value when we cannot

2005-04-12 Thread mueller at kde dot org
--- Additional Comments From mueller at kde dot org 2005-04-13 01:36 --- looking at it - the artsd crash is not reproduceable for me. is this one still there? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19317

[Bug regression/20973] [4.0/4.1 Regression] kdelibs (khtml) miscompiled by reload

2005-04-12 Thread mueller at kde dot org
--- Additional Comments From mueller at kde dot org 2005-04-13 01:54 --- will test the patch with a KDE recompilation. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20973

[Bug c++/19317] [4.1 Regression] removing a temporary return value when we cannot

2005-04-13 Thread mueller at kde dot org
--- Additional Comments From mueller at kde dot org 2005-04-13 16:57 --- can we think about retargeting fixing the optimisation for 4.0.1 ? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19317

[Bug libstdc++/19664] libstdc++ headers should have pop/push of the visibility around the declarations

2005-10-21 Thread mueller at kde dot org
--- Comment #70 from mueller at kde dot org 2005-10-21 11:36 --- whats the status of the patch? can we at least have the visibility push/pop patch for libstdc++ in gcc 4.0.x branch? Marc: what is the reason this patch is rejected? sure its not a regression, but visibility support is

[Bug libstdc++/19664] libstdc++ headers should have pop/push of the visibility around the declarations

2005-10-23 Thread mueller at kde dot org
--- Comment #72 from mueller at kde dot org 2005-10-24 05:22 --- why is it pointless? just because it doesn't work on some target architectures doesn't mean it doesn't work on most main archs. I find it pointless that a patch isn't applied just because it doesn&

[Bug libstdc++/19664] libstdc++ headers should have pop/push of the visibility around the declarations

2005-10-25 Thread mueller at kde dot org
--- Comment #74 from mueller at kde dot org 2005-10-25 15:41 --- yes, well one reason for it is that several libs (e.g. libgcc2) already use push/pop visibility macros and it doesn't seem to harm. furthermore I manually added push/pop macros to libstdc++ headers on a debian s

[Bug libstdc++/19664] libstdc++ headers should have pop/push of the visibility around the declarations

2005-10-31 Thread mueller at kde dot org
--- Comment #80 from mueller at kde dot org 2005-10-31 22:45 --- - if its not safe for all architectures we'd already run into heaps of problems because both libsupc++ and libgcc2 already include similiar pragmas. - not hiding a symbols is better than the resulting issues when h

[Bug middle-end/24627] New: [4.1 Regression] xntp miscompiled

2005-11-01 Thread mueller at kde dot org
: middle-end AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: mueller at kde dot org GCC host triplet: i686-gnu-linux http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24627

[Bug middle-end/24627] [4.1 Regression] xntp miscompiled

2005-11-01 Thread mueller at kde dot org
--- Comment #1 from mueller at kde dot org 2005-11-01 23:06 --- Created an attachment (id=10110) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=10110&action=view) testcase -O1 or higher exposes the bug. -fno-tree-dce or undoing commit 101841 fixes it. -- http://gcc.

[Bug c/22537] New: unable to find a register to spill in cl

2005-07-17 Thread mueller at kde dot org
Product: gcc Version: 4.0.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: mueller at kde dot org CC: gcc-bugs at gcc dot gnu dot org GCC host tri

[Bug c/22537] unable to find a register to spill in cl ass ‘CREG’

2005-07-17 Thread mueller at kde dot org
-- What|Removed |Added Keywords||ice-on-valid-code Summary|unable to find a register to|unable to find a register to

[Bug middle-end/22592] -fvisibility-inlines-hidden broken differently

2005-07-21 Thread mueller at kde dot org
-- What|Removed |Added CC||mueller at kde dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22592

[Bug rtl-optimization/17700] -Os causes bad build of libgcj.so.5.0.0 file

2005-08-14 Thread mueller at kde dot org
-- What|Removed |Added CC||mueller at kde dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17700

[Bug target/15617] building groff-1.19.1 with "-Os -march=pentium4" causes sig 11

2005-08-14 Thread mueller at kde dot org
--- Additional Comments From mueller at kde dot org 2005-08-15 00:46 --- duplicate of #13685 ? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15617

[Bug c++/22063] New: link failure involving symbol visibility

2005-06-14 Thread mueller at kde dot org
t: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: mueller at kde dot org CC: gcc-bugs at gcc dot gnu dot org GCC target triplet: i386-suse-linux http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22063

[Bug c++/22063] link failure involving symbol visibility

2005-06-14 Thread mueller at kde dot org
--- Additional Comments From mueller at kde dot org 2005-06-14 14:19 --- Created an attachment (id=9088) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=9088&action=view) testcase -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22063

[Bug c++/14755] [3.4/3.5 regression] miscompilation in bitfielded signed integers

2004-03-27 Thread mueller at kde dot org
--- Additional Comments From mueller at kde dot org 2004-03-27 16:58 --- why is this not targetted against 3.4.0 ? this is a severe miscompilation, you cannot run any of Qt or KDE this way :( -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14755

[Bug c++/19190] New: [4.0 regression] warning "value computed is not used" emitted too often

2004-12-29 Thread mueller at kde dot org
Priority: P2 Component: c++ AssignedTo: mmitchel at gcc dot gnu dot org ReportedBy: mueller at kde dot org CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: i686-pc-linux-

[Bug c++/19190] [4.0 regression] warning "value computed is not used" emitted too often

2004-12-29 Thread mueller at kde dot org
--- Additional Comments From mueller at kde dot org 2004-12-30 03:51 --- Many thanks for your quick fix! -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19190

[Bug c++/19317] New: forgets to deep-copy temporary return value

2005-01-07 Thread mueller at kde dot org
atus: UNCONFIRMED Severity: critical Priority: P2 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: mueller at kde dot org CC: gcc-bugs at gcc dot gnu dot org,mark at codesourcery dot com GCC build t

[Bug c++/19317] forgets to deep-copy temporary return value

2005-01-07 Thread mueller at kde dot org
-- What|Removed |Added Keywords||wrong-code http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19317

[Bug ada/19220] Return-by-reference type wrongly considered return-by-copy

2005-01-16 Thread mueller at kde dot org
--- Additional Comments From mueller at kde dot org 2005-01-16 15:19 --- can this be targetted at 4.0 milestone please? -- What|Removed |Added CC

[Bug middle-end/19585] internal compiler error: Segmentation fault in gen_decl_die

2005-01-23 Thread mueller at kde dot org
-- What|Removed |Added CC||mueller at kde dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19585

[Bug c++/19474] wrong tree for extern "C" variables

2005-01-23 Thread mueller at kde dot org
-- What|Removed |Added CC||mueller at kde dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19474

[Bug c++/19317] [4.0 Regression] removing a temporary return value when we cannot

2005-02-13 Thread mueller at kde dot org
--- Additional Comments From mueller at kde dot org 2005-02-13 14:59 --- bug has been fixed by 2005-02-13 Jason Merrill <[EMAIL PROTECTED]> PR mudflap/19319 * gimplify.c (gimplify_modify_expr_rhs) [CALL_EXPR]: Make return slot ex

[Bug tree-optimization/17661] ICE in create_tmp_var

2004-10-12 Thread mueller at kde dot org
--- Additional Comments From mueller at kde dot org 2004-10-12 15:41 --- Please reopen this bugreport, its not a duplicate of 17554 and still unfixed (while 17554 is fixed). -- What|Removed |Added

[Bug tree-optimization/17661] ICE in create_tmp_var

2004-10-12 Thread mueller at kde dot org
--- Additional Comments From mueller at kde dot org 2004-10-12 15:42 --- reduced testcase: struct C { int *c; C () : c (0) { } C (const C &x) : c (x.c) { } C &operator++ () { return *this; } }; void breakme (void) { C j; bool k = false; for (

[Bug c++/18369] New: [4.0 regression] Segfault on braced new

2004-11-07 Thread mueller at kde dot org
gcc Version: 4.0.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: mueller at kde dot org CC: gcc-bugs at gcc dot gnu dot org GCC build trip

[Bug c++/18369] [4.0 regression] Segfault on braced new

2004-11-07 Thread mueller at kde dot org
-- What|Removed |Added Severity|normal |critical Keywords||ice-on-valid-code http://gcc.gnu.org/bugzilla/show_b

[Bug middle-end/18477] New: Wsequence-point false positive

2004-11-14 Thread mueller at kde dot org
mary: Wsequence-point false positive Product: gcc Version: 4.0.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: middle-end AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: mueller at kde dot org

[Bug middle-end/18477] Wsequence-point false positive

2004-11-14 Thread mueller at kde dot org
-- What|Removed |Added Keywords||diagnostic http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18477