--- Comment #2 from lennox at cs dot columbia dot edu 2010-08-11 20:01
---
This problem still exists in GCC 4.5.1.
--
lennox at cs dot columbia dot edu changed:
What|Removed |Added
--- Comment #1 from lennox at cs dot columbia dot edu 2010-07-13 18:54
---
Adding Cc: of Ian Taylor -- this message is emitted by
warn_cxx_compat_finish_struct, written by him.
--
lennox at cs dot columbia dot edu changed:
What|Removed |Added
27;-v' '-c' '-mtune=generic'
'-march=i486'
--
Summary: -Wc++-compat warns incorrectly for anonymous unions
[regression from 4.4]
Product: gcc
Version: 4.5.0
Status: UNCONFIRMED
Severity: norma
--- Comment #2 from lennox at cs dot columbia dot edu 2010-02-25 15:31
---
Note that (as with PR 34000) this appears to be a regression from GCC 4.2.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42951
nueabi/4.4.2/../../../../arm-linux-gnueabi/lib/
COLLECT_GCC_OPTIONS='-v' '-mfpu=neon' '-c' '-march=armv7-a' '-mtune=cortex-a8'
'-mfloat-abi=softfp'
--
Summary: GCC pedwarns about use of static inline functions from
--- Comment #7 from lennox at cs dot columbia dot edu 2008-08-11 14:11
---
The fact that the function returns the vector is not an essential part of the
test; the return value of the load function just needs not to be optimized out
as unused. So changing the test for broader
; '-mtune=generic'
--
Summary: Strict-aliasing warnings are printed for _mm_load_si128,
even though __m128i is __attribute__((__may_alias__)).
Product: gcc
Version: 4.3.2
Status: UNCONFIRMED
Severity: normal
--- Comment #18 from lennox at cs dot columbia dot edu 2008-02-20 05:03
---
This is a regression from 4.2, despite the lack of marking.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34000
--- Comment #16 from lennox at cs dot columbia dot edu 2008-02-19 21:01
---
Is there any possibility of getting a fix for this into 4.3.0?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34000
--- Comment #15 from lennox at cs dot columbia dot edu 2008-02-13 22:27
---
Arguably, the use of static data (possible excepting const static data) or a
non-inline static function is worthy of a pedwarn. But I'd certainly be
inclined to agree for static inline functions.
--
--- Comment #13 from lennox at cs dot columbia dot edu 2008-02-13 04:38
---
Linking when the functions can't be inlined would be the only gotcha, but that
would mean that the new attachment (func-pointer-sse.c) would regress.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34000
--- Comment #12 from lennox at cs dot columbia dot edu 2008-02-13 04:35
---
Created an attachment (id=15134)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15134&action=view)
test program using pointers to functions from emmintrin.h
--
http://gcc.gnu.org/bugzilla/show_
--- Comment #10 from lennox at cs dot columbia dot edu 2008-02-12 22:46
---
The right answer is probably to declare the system header functions "inline"
when __GNUC_STDC_INLINE__, otherwise "extern inline"; or equivalently to
declare them "extern inline __at
--- Comment #8 from lennox at cs dot columbia dot edu 2008-02-12 21:37
---
The attachment (inline-test-sse.c) on this PR is the gnu89 version of the
problem.
On MacOS X 10.5.2 (Apple gcc 5465), which has the same code as mainline FSF
GCC, it prints:
inline-test-sse.c: In function
--- Comment #6 from lennox at cs dot columbia dot edu 2008-02-12 15:49
---
(In reply to comment #4)
The problem occurs equally with gnu89 "extern inline" functions as with c99
"inline" functions (as seen in the initial bug report), so using static inline
when !
--- Comment #3 from lennox at cs dot columbia dot edu 2008-02-11 19:51
---
A discussion on comp.std.c
<http://groups.google.com/group/comp.std.c/browse_thread/thread/8118ae4c53a4de60>
indicates that this is indeed a constraint violation; the poster thinks that
system headers sho
--- Comment #2 from lennox at cs dot columbia dot edu 2008-01-30 18:28
---
Created an attachment (id=15058)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15058&action=view)
test program illustrating the warning about static inline functions, using
emmintrin.h
--
--- Comment #1 from lennox at cs dot columbia dot edu 2008-01-30 18:26
---
The static const data problem is also PR 35017, now fixed; I'm editing the
summary accordingly.
The problem with static inline functions is not restricted to Darwin. The
following example shows the probl
LLECT_GCC_OPTIONS='-mmacosx-version-min=10.5.0' '-c' '-v' '-mtune=generic'
This problem appears to have been introduced by Geoffrey Keating in Subversion
Revision 118356, a fix for PR 11377.
GCC 4.2 does not have this problem.
--
Summary: G
--- Comment #2 from lennox at cs dot columbia dot edu 2005-12-06 21:31
---
Created an attachment (id=10427)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=10427&action=view)
Custom debug allocator, based on libstdc++'s malloc_allocator.
--
http://gcc.gnu.
--- Comment #1 from lennox at cs dot columbia dot edu 2005-12-06 21:30
---
Created an attachment (id=10426)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=10426&action=view)
C source file, constructing a list with a custom debug allocator.
--
http://gcc.gnu.org/b
t: gcc
Version: 4.0.3
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: lennox at cs dot columbia dot edu
GCC build triplet: i386-portbld-freebsd5.4
G
--- Additional Comments From lennox at cs dot columbia dot edu 2005-08-25
17:23 ---
Created an attachment (id=9585)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=9585&action=view)
C++ source file that produces warning with GCC 4.0.2
This file does not #include any files,
004-05-23
--
Summary: False warning for uninitialized variable: regression
from 3.4.2
Product: gcc
Version: 4.0.2
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: tree-optimization
Assigned
24 matches
Mail list logo
