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=58236
--- Comment #1 from Marc Glisse glisse at gcc dot gnu.org ---
Note, from the documentation of -Wuninitialized:
Because these warnings depend on optimization, the exact variables or elements
for which there are warnings depends on the precise
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57843
janus at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50392
--- Comment #7 from Vittorio Zecca zeccav at gmail dot com ---
Still in gfortran 4.8.1.
In trans-stmt.c:105
len = GFC_DECL_STRING_LEN (se.expr);
the pointer se.expr-decl_common.lang_specific is NULL.
Thus causing the segmentation fault.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58220
Kazumoto Kojima kkojima at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58236
--- Comment #2 from Noufal Ibrahim noufal at nibrahim dot net.in ---
That solves the issue although I find the relationship between the
optimisations and the warnings somewhat tenuous atleast from a user
perspective. Would it not be a good idea to
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58185
janus at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58229
--- Comment #2 from janus at gcc dot gnu.org ---
(In reply to janus from comment #1)
The second one is the allocate-on-assignment inside the function, which
nevers gets freed. This *is* a bug. What should be done is: Create a
temporary for the
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58229
janus at gcc dot gnu.org changed:
What|Removed |Added
Summary|[F03] Memory leak with |[F03] Memory leak with
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58208
--- Comment #3 from Mikael Pettersson mikpe at it dot uu.se ---
I can't reproduce the SEGV on Fedora 17 with gcc-4.8.1 -m32 or gcc-4.9 -m32.
However, I think the build recipe is flawed. If I follow it to the letter
(with -Wl,-rpath pointing to
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57798
Mikael Morin mikael at gcc dot gnu.org changed:
What|Removed |Added
Summary|[4.8 Regression] Incorrect |Incorrect
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57798
Mikael Morin mikael at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58237
Bug ID: 58237
Summary: gcc fails to detect obvious resource leaks
Product: gcc
Version: 4.9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58238
Bug ID: 58238
Summary: cc1 crashes when built for ms-dos cross-compiling
Product: gcc
Version: 4.7.3
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58158
--- Comment #7 from Aaro Koskinen aaro.koskinen at iki dot fi ---
Loongson 2F is MIPS III + movz/movn only. I am currently running my compiler
with the below workaround, and it seems to help:
--- gcc-4.8.1.orig/gcc/config/mips/mips.md
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58153
--- Comment #3 from François Dumont fdumont at gcc dot gnu.org ---
This report entry made me wonder why iterators could not just be pointing to
the node just before the one containing the pointed to value. For instance
begin() iterator would
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58208
--- Comment #4 from Tammy Hsu tammy at Cadence dot COM ---
Sorry, I forgot to mention that I need to set LD_LIBRARY_PATH to . to run
import.
I build the gcc473 and gcc481 by using the same configuration and on the same
RHEL 5.5 system, however the
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58153
--- Comment #4 from Kenton Varda temporal at gmail dot com ---
This report entry made me wonder why iterators could not just be
pointing to the node just before the one containing the pointed to value.
That's a neat idea.
I think there is an
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57982
Andrew Pinski pinskia at gcc dot gnu.org changed:
What|Removed |Added
Target||i686-*-mingw32
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53025
--- Comment #3 from Daniel Krügler daniel.kruegler at googlemail dot com ---
This is just a polite reminder for some response. I'm especially interested to
hear whether there exist any reasonable doubts on the validity of the arguments
brought
20 matches
Mail list logo
