--- Comment #3 from mec at google dot com 2009-07-31 16:04 ---
Subject: Re: gcc -Waddress lost some useful warnings
Yes, I think this is a bug, because the behavior of gcc doesn't match
its documentation.
First, I think the C++ standard forbids a function from having a null
address
at gcc dot gnu dot org
ReportedBy: mec at google dot com
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35927
--- Comment #5 from mec at google dot com 2008-04-04 16:36 ---
Doh! You are right, I was confused when I read z1.cc:2:4 as an error on line
4. Both errors are in line 2, inside the #if block. Sorry for the noise.
--
mec at google dot com changed:
What|Removed
at google dot com
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33925
to initialize array members
Product: gcc
Version: 4.2.2
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: mec at google dot com
GCC build triplet: i686
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: mec at google dot com
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi
--- Comment #1 from mec at google dot com 2007-10-12 16:08 ---
Created an attachment (id=14349)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14349action=view)
Test program
Compile with: g++ -Wall -c z4.cc
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33752
--- Comment #2 from mec at google dot com 2007-09-21 05:59 ---
Created an attachment (id=14237)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14237action=view)
Test program
Compile with: gcc -Wall -S z3.cc
This program does give a warning about a1 defined-but-not-used. I believe
: Inconsistent warning for compile-time integer overflow
Product: gcc
Version: 4.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: mec at google dot
--- Comment #1 from mec at google dot com 2007-09-21 05:28 ---
Created an attachment (id=14235)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14235action=view)
Test program
Compile with: gcc -Wall -S z5.cc
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33514
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: mec at google dot com
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://gcc.gnu.org
--- Comment #1 from mec at google dot com 2007-09-21 05:58 ---
Created an attachment (id=14236)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14236action=view)
Test program
compile with: gcc -Wall -S z2.cc
This program does not give a warning about a1 defined-but-not-used. I
--- Comment #8 from mec at google dot com 2007-09-03 15:47 ---
DR 354 has been in state WP since October 2005. Is that good enough to
unsuspend this issue?
http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_defects.html#354
--
mec at google dot com changed:
What
ignore trigraphs in /* */ comments
Product: gcc
Version: 4.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: preprocessor
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: mec at google dot com
GCC
--- Comment #1 from mec at google dot com 2007-08-22 00:35 ---
Created an attachment (id=14093)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14093action=view)
C++ source file with trigraphs in comments and #if 0
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33143
--- Comment #2 from mec at google dot com 2007-08-20 19:31 ---
new T[0] looks like defined behavior to me.
[expr.new] 5.3.4 -7-
When the value of the expression in a direct-new-declarator is zero, the
allocation function is called to allocate an array with no elements. The
pointer
.
--
Summary: i686 sse2 generates more movdqa than necessary
Product: gcc
Version: 4.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: mec at google
--- Comment #1 from mec at google dot com 2007-07-12 01:30 ---
Created an attachment (id=13894)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13894action=view)
Test program
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32735
--- Comment #2 from mec at google dot com 2007-07-12 01:31 ---
Created an attachment (id=13895)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13895action=view)
Generated code
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32735
--- Comment #3 from mec at google dot com 2007-07-12 01:33 ---
Created an attachment (id=13896)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13896action=view)
Assembly code
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32735
--- Comment #4 from mec at google dot com 2007-07-12 01:33 ---
Created an attachment (id=13897)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13897action=view)
Assembly code
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32735
Status: UNCONFIRMED
Severity: trivial
Priority: P3
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: mec at google dot com
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc
--- Comment #22 from mec at google dot com 2007-06-15 13:15 ---
With the test program, gcc 4.1.2 generates correct code and gcc 4.2.0 generates
wrong code. Can someone increase the priority and severity of this PR?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32327
--- Comment #12 from mec at google dot com 2007-06-04 13:35 ---
Verified with my two test programs with snapshot gcc-4.3-20070601. Thanks for
the fast fix!
--
mec at google dot com changed:
What|Removed |Added
Priority: P3
Component: libstdc++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: mec at google dot com
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id
Product: gcc
Version: 4.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: mec at google dot com
GCC build triplet: i686-pc-linux-gnu
GCC
--- Comment #7 from mec at google dot com 2007-05-30 23:01 ---
I think the problem is independent of __is_pod. The new
std::uninitialized_fill has an if statement, not a template specialization.
Compilation always attempts to instantiate std::fill(__first_, __last_, __x),
whether
at google dot com
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32102
Version: 4.1.2
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: mec at google dot com
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC
: 4.1.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: mec at google dot com
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC
: unassigned at gcc dot gnu dot org
ReportedBy: mec at google dot com
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28408
Priority: P3
Component: libstdc++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: mec at google dot com
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28277
--- Comment #2 from mec at google dot com 2006-07-05 22:20 ---
Sure, here is a test program for versa_string:
// Copyright 2006, Google Inc. All rights reserved.
// Author: [EMAIL PROTECTED] (Michael Chastain)
//
// Test operator(ostream, const versa_string)
#include ext/vstring.h
--- Comment #5 from mec at google dot com 2006-07-05 22:43 ---
The threads point is just a basic stack size issue: threads on linux have a
fixed size which is often smaller than the main stack size limit.
With an output width of 60 million, it's easy to see a failure, even on a main
Product: gcc
Version: 4.1.0
Status: UNCONFIRMED
Severity: major
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: mec at google dot com
GCC build triplet: i686-pc-linux-gnu
GCC host
--- Comment #1 from mec at google dot com 2006-05-14 16:55 ---
Created an attachment (id=11463)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=11463action=view)
C++ source code
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27603
--- Comment #11 from mec at google dot com 2006-01-21 22:04 ---
You can make this visible at the C++ program level with a Key class that has a
signature field. Init the signature in the constructor, clear the signature in
the destructor, and check the signature in operator
: 4.0.2
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: mec at google dot com
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC
++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: mec at google dot com
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24745
++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: mec at google dot com
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24746
--- Additional Comments From mec at google dot com 2005-09-03 20:16 ---
Here is another test with confirmatory data.
Test case, reduced from some firefox code:
int punycode_decode(const char input[], unsigned char case_flags[])
{
int j;
for (j = 0; j 128; ++j
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: mec at google dot com
CC: dank at kegel dot com,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-gnu
--- Additional Comments From mec at google dot com 2005-08-22 06:59 ---
Created an attachment (id=9551)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=9551action=view)
source file to demonstrate wrong code
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23512
43 matches
Mail list logo
