http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58236
Bug ID: 58236
Summary: -Wuninitialized doesn't report uninitialised variable
as expected
Product: gcc
Version: 4.8.0
Status: UNCONFIRMED
Severity: normal
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54485
Paolo Carlini changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned at
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56779
--- Comment #4 from Dâniel Fraga ---
Nobody?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58235
--- Comment #4 from farouk jouti ---
the link contains all the necessary information about the bug (just check the
comments and answers) ;)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58235
farouk jouti changed:
What|Removed |Added
CC||farouk.jouti at live dot co.uk
--- Comment
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58061
--- Comment #3 from Whitequill Riclo ---
I can not proceseed with a project due to this bug, is there anything I can do
in the mean time?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58234
--- Comment #6 from Larry Baker ---
Thank you.
The example I found (mov_blk) that does not use output constraints, but
specifies that the input registers are clobbered, is from a 2003 document. It
too fails using today's gcc.
I appreciate your
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58234
--- Comment #5 from Andrew Pinski ---
> Can you tell me how it is possible to specify the clobber side effects without
> requiring output constraints?
It is too hard if you have inputs in those registers too. You could push/pop
on the stack thos
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58235
--- Comment #2 from Olivier Gay ---
Still, constraint of assignment (c90, 6.3.16) requires the left operand of
assignment to be a modifiable lvalue. But c object array is not a modifiable
lvalue as arrays are not modifiable lvalues (6.2.2.1).
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58234
--- Comment #4 from Larry Baker ---
Actually, there is: the useless movl instead of a movq of the updated address
pointer into __d1 on x86_64. But, that is a benign flaw.
Can you answer either of my questions?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58235
--- Comment #1 from Andrew Pinski ---
This seems correct: See also bug 461. non-lvalue arrays do not decay to
pointers in C90/C89.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58234
--- Comment #3 from Andrew Pinski ---
(In reply to Larry Baker from comment #2)
> Andrew,
>
> Thank you for your prompt reply. Fair enough.
>
> Can you direct me to where glibc bugs are reported?
Except there is no bug in glibc's headers as I
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58208
Andrew Pinski changed:
What|Removed |Added
Keywords||wrong-code
Severity|major
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58234
--- Comment #2 from Larry Baker ---
Andrew,
Thank you for your prompt reply. Fair enough.
Can you direct me to where glibc bugs are reported?
I have already filed a bug report with Intel.
The in-line asm is not quite correct. But the flaw is
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58208
Tammy Hsu changed:
What|Removed |Added
Severity|normal |major
--- Comment #2 from Tammy Hsu ---
Can
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58234
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58235
Bug ID: 58235
Summary: Missing diagnostic on assignment to array in c89
Product: gcc
Version: 4.8.1
Status: UNCONFIRMED
Severity: minor
Priority: P3
Component: c
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58234
Bug ID: 58234
Summary: In-line asm version of __FD_ZERO in
/usr/include/bits/select.h
Product: gcc
Version: 4.4.7
Status: UNCONFIRMED
Severity: normal
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39029
Johan Boulé changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57610
--- Comment #9 from Hubert Tong ---
CWG 1604 may address the issues with performance and slicing mentioned in CWG
1287 which led to CWG 1650.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58233
Bug ID: 58233
Summary: null pointer cm in gfc_conv_structure at
fortran/trans-expr.c:6132
Product: gcc
Version: 4.8.1
Status: UNCONFIRMED
Severity: normal
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57610
Hubert Tong changed:
What|Removed |Added
CC||hstong at ca dot ibm.com
--- Comment #8 fro
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58232
Bug ID: 58232
Summary: False mudflap positive on std::setw
Product: gcc
Version: 4.8.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libmudflap
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57798
Mikael Morin changed:
What|Removed |Added
Summary|[4.8/4.9 Regression]|[4.8 Regression] Incorrect
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58229
janus at gcc dot gnu.org changed:
What|Removed |Added
Keywords||wrong-code
Status|U
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58223
--- Comment #4 from Marek Polacek ---
Ok, so what happens here is that rdg_build_partitions builds two partitions,
that essentially means we split the loop in the original test case into two
loops:
for (b = 0; b < 2; b++)
a[0] = 1;
for (
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58221
--- Comment #8 from Teresa Johnson ---
Tested on x86_64-unknown-linux-gnu, and also reproduced the failure
listed in PR rtl-optimization/58220 and verified the fix with it.
Committed as r201941:
Index: final.c
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58221
--- Comment #7 from Teresa Johnson ---
On Fri, Aug 23, 2013 at 6:49 AM, kkojima at gcc dot gnu.org
wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58221
>
> --- Comment #6 from Kazumoto Kojima ---
> (In reply to Teresa Johnson from comment
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58221
--- Comment #6 from Kazumoto Kojima ---
(In reply to Teresa Johnson from comment #5)
> Kaz, are you planning to apply your patch, or do you want me to test
> it and commit it? I'm kicking off x86_64 tests with it right now, but
> I didn't get the
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58221
--- Comment #5 from Teresa Johnson ---
Thanks, and sorry for the trouble.
Kaz, are you planning to apply your patch, or do you want me to test
it and commit it? I'm kicking off x86_64 tests with it right now, but
I didn't get the failure on that
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58221
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #4 f
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58143
--- Comment #13 from Jakub Jelinek ---
Because the bug is in lim, so hacking around it in other parts of the compiler
and removing desirable optimizations just to mitigate the bug is not the right
way to fix it.
Either lim shouldn't move the expr
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58221
Kazumoto Kojima changed:
What|Removed |Added
CC||kkojima at gcc dot gnu.org
--- Comment
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58221
Hans-Peter Nilsson changed:
What|Removed |Added
Last reconfirmed||2013-08-23
CC|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58143
--- Comment #12 from Bernd Edlinger ---
(In reply to Jakub Jelinek from comment #11)
> No, that is wrong as well.
Because it is too destructive? Maybe.
I think this is a general problem here.
1. the undefined behavior warning may be triggered b
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55677
Paolo Carlini changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55677
Paolo Carlini changed:
What|Removed |Added
Resolution|INVALID |WORKSFORME
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50436
--- Comment #3 from Paolo Carlini ---
Currently both hang for me (after a rather useful error message). We can
certainly do better, of course. Interesting that the error messages produced by
clang and icc are completely different.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58231
Marek Polacek changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58231
Bug ID: 58231
Summary: Using post-decrement as a boolean expression in if
statement leads to crash
Product: gcc
Version: 4.6.2
Status: UNCONFIRMED
Severity: norm
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58221
--- Comment #1 from Hans-Peter Nilsson ---
No significant change in results for regress-446 -> regress-444 for r201882
from r201874 (some libstdc++ changes pass again, but others now fail). Maybe
r201883 is the winner; checking.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58218
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58230
Bug ID: 58230
Summary: mutliple test fail in german language version
Product: gcc
Version: 4.9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libm
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58229
Bug ID: 58229
Summary: Memory leak with overloaded operator
Product: gcc
Version: 4.9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58228
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
Target Milesto
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58143
--- Comment #11 from Jakub Jelinek ---
No, that is wrong as well.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58143
Bernd Edlinger changed:
What|Removed |Added
Attachment #30681|0 |1
is obsolete|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58113
Bernd Edlinger changed:
What|Removed |Added
CC||bernd.edlinger at hotmail dot
de
--- Co
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58228
Marek Polacek changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58227
Marek Polacek changed:
What|Removed |Added
Known to work||4.8.1
Target Milestone|---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58223
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #3 f
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58227
Marek Polacek changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58228
Bug ID: 58228
Summary: wrong code (with vectorization?) at -O3 on
x86_64-linux-gnu
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
P
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58227
--- Comment #2 from Zhendong Su ---
But similar to 58143, because of short circuiting (since a == 0), the
expression "0 < -2147483647 - h ? 0 : 1" shouldn't be evaluated at all,
correct? Or maybe I'm mistaken?
Thanks for looking into this Mare
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58209
Jakub Jelinek changed:
What|Removed |Added
Known to work||4.8.2, 4.9.0
Summary|[4.7/4.8/
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58227
Marek Polacek changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
--- Comment #
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57932
Markus Eisenmann changed:
What|Removed |Added
Target|IA-32/x86-64|i386
--- Comment #1 from Markus Eisenm
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58227
Bug ID: 58227
Summary: wrong code (hangs) at -O3 on x86_64-linux-gnu
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tr
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58223
Marek Polacek changed:
What|Removed |Added
Known to work||4.7.3
Target Milestone|---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58223
Marek Polacek changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
--- Comment #
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58223
Marc Glisse changed:
What|Removed |Added
Keywords||wrong-code
Status|UNCONFIRMED
61 matches
Mail list logo