http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48782
Summary: unused-but-set static variables are not optimized out
Product: gcc
Version: 4.6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
AssignedTo:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48779
Summary: -Wunused-but-set-variable does not report unread
unit-static variables
Product: gcc
Version: 4.6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
--- Comment #1 from flameeyes at gentoo dot org 2009-12-04 22:43 ---
Created an attachment (id=19229)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19229&action=view)
Patch to fix the problem
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42289
ormal
Priority: P3
Component: libffi
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: flameeyes at gentoo dot org
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: arm-*-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42289
--- Comment #1 from flameeyes at gentoo dot org 2009-12-04 15:06 ---
Created an attachment (id=19224)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19224&action=view)
Proposed patch
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42276
everity: normal
Priority: P3
Component: java
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: flameeyes at gentoo dot org
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: arm-*-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42276
--- Comment #6 from flameeyes at gentoo dot org 2009-12-04 12:54 ---
Created an attachment (id=19222)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19222&action=view)
Proposed patch
With this patch applied, gcj cross-builds fine (not a canadian cross though).
--
--- Comment #1 from flameeyes at gentoo dot org 2009-08-06 15:10 ---
I can confirm this issue on 4.3.3 as well.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40989
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: flameeyes at gentoo dot org
GCC host triplet: x86_64-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40989
--- Comment #6 from flameeyes at gentoo dot org 2009-07-06 17:03 ---
To be honest there are quite a few default warnings that I wouldn't want to
turn into errors, but it would still be better than having _no_ way to get this
into an error.
--
http://gcc.gnu.org/bug
--- Comment #3 from flameeyes at gentoo dot org 2008-11-13 17:20 ---
The same happens for "assignment makes integer from pointer without a cast" .
It really is not nice that these warnings cannot be made errors explicitly,
they are _quite_ important.
--
http://gcc.gnu.or
--- Comment #6 from flameeyes at gentoo dot org 2008-10-21 23:48 ---
Created an attachment (id=16525)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16525&action=view)
Preprocessed test case
That's because I forgot to turn on -O2 :/
tc-htons-unrechable.c: In function
--- Comment #4 from flameeyes at gentoo dot org 2008-10-21 23:19 ---
Created an attachment (id=16524)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16524&action=view)
Preprocessed test case
For what it's worth this is glibc 2.8 on Gentoo, AMD64 multilib system.
--- Comment #2 from flameeyes at gentoo dot org 2008-10-21 22:56 ---
Created an attachment (id=16523)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16523&action=view)
tc-htons-unreachable.c
Sure here it is, there isn't much of a testcase I admit ;)
--
http:/
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: flameeyes at gentoo dot org
GCC build triplet: x86_64-pc-linux-gnu
GCC host triplet: x86_64-pc-linux-gnu
GCC target triplet: x86_64-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37881
--- Comment #2 from flameeyes at gentoo dot org 2008-10-17 22:36 ---
Which gives it even more usefulness to be optionally treated as an error, since
it really helps to avoid shooting oneself in the foot...
I guess it would be bad to have a way to -Wno- it, but it would be nice to at
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: flameeyes at gentoo dot org
GCC build triplet: x86_64-pc-linux-gnu
GCC host triplet: x86_64-pc-linux-gnu
GCC target triplet: x86_
--- Comment #4 from flameeyes at gentoo dot org 2008-05-11 16:31 ---
I think this applies to 4.3 as well, as the following code does only warn in
the second function:
#include
#include
char* oldstyle(const char *foo) {
size_t foolen;
if ( foo == NULL )
return NULL
--- Comment #3 from flameeyes at gentoo dot org 2006-06-29 12:17 ---
Sorry, I think I misunderstood the error messages' chain, as when the
__attribute__ is malformed (forgot a '('), the warning about the possible
candidate appear anyway, so i thought it was simply being
--- Comment #1 from flameeyes at gentoo dot org 2006-06-29 11:27 ---
Created an attachment (id=11780)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=11780&action=view)
impossible-missing-format-attribute.c
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28199
vprintf() like functions
Product: gcc
Version: 4.1.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: flameeyes at gentoo dot org
GCC build triplet:
--- Comment #4 from flameeyes at gentoo dot org 2006-06-15 23:30 ---
This is still an issue in 4.1.1.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25272
22 matches
Mail list logo
