tatus: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: qrczak at knm dot org dot pl
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
--- Comment #1 from qrczak at knm dot org dot pl 2006-08-14 19:00 ---
Created an attachment (id=12075)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12075&action=view)
Test case
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28727
--- Comment #3 from qrczak at knm dot org dot pl 2006-08-26 19:15 ---
The problem seems to be caused by illegal type punning. Rewriting the code to
avoid pointer casts cures the bug, and -fno-strict-aliasing cures it too, so
gcc is probably correct.
Thanks to Michael Veksler for
dot org
ReportedBy: qrczak at knm dot org dot pl
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=28865
--- Comment #1 from qrczak at knm dot org dot pl 2006-08-27 22:15 ---
A question: when this is fixed, what should be C-level sizeof obj?
I hope it would include the flexible array component. This would allow to
detect in autoconf whether this bug is fixed, and would be consistent with
--- Additional Comments From qrczak at knm dot org dot pl 2005-02-20 10:16
---
> You cannot create code that works with this option and doesn't work without it
> except by violating the POSIX standard. So POSIX code should not have this
> option enabled by default
--- Additional Comments From qrczak at knm dot org dot pl 2005-02-20 13:00
---
> There is certainly the eternal argument whether a class should implement its
> own
> locks internally or whether the caller should implement them.
And my guideline is as follows: it should impl
--- Additional Comments From qrczak at knm dot org dot pl 2005-02-20 21:43
---
> >Static locals in C++ are an equivalent to pthread_once in C/POSIX.
>
> Even in the single-threaded case, C++ leaves it undefined what happens if you
> reenter a function that invokes a sta
--- Additional Comments From qrczak at knm dot org dot pl 2005-02-23 01:53
---
> The '-pthreads' flag should imply '-fno-threadsafe-statics'. For every other
> similar flag I can find, the default is to permit the compiler to make the
> optimizations that
--- Additional Comments From qrczak at knm dot org dot pl 2005-02-24 17:31
---
> "multithreading is defined by an application design that ALLOWS FOR concurrent
> or simultaneous execution"
Initializers of static locals cannot execute concurrently, no matter
--- Additional Comments From qrczak at knm dot org dot pl 2005-02-24 21:06
---
> First, if we're talking about pthreads programs, which is the only case I'm
> suggesting removing the locking for, then those programs are already broken.
They are non-portable no m
--- Additional Comments From qrczak at knm dot org dot pl 2005-02-24 22:37
---
> By your definition of MT-safe, almost no function is MT-safe. Is 'strchr'
> MT-safe if you call it on a string while another function might modify that
> string? No, so lets put aut
ed at gcc dot gnu dot org
ReportedBy: qrczak at knm dot org dot pl
CC: 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
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20550
--- Additional Comments From qrczak at knm dot org dot pl 2005-03-20 19:10
---
> Better than that the availability of something like
> #pragma expected-warning line WARNING-NAME
> might remove the warning generated by the following line labeling it as
> checked,
>
4.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: qrczak at knm dot org dot pl
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
ion: 4.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: qrczak at knm dot org dot pl
CC: gcc-bugs at gcc dot gnu dot org
GCC build triplet: i686-pc-linux-gnu
--- Additional Comments From qrczak at knm dot org dot pl 2005-08-31 22:11
---
> I think this is fixed by the patch for PR 23509:
> http://gcc.gnu.org/ml/gcc-patches/2005-08/msg01647.html
Indeed, applying this patch and recompiling gcc fixed the bug. Thanks.
--
http://gcc.g
--- Additional Comments From qrczak at knm dot org dot pl 2005-08-31 22:23
---
*** This bug has been marked as a duplicate of 23509 ***
--
What|Removed |Added
--- Additional Comments From qrczak at knm dot org dot pl 2005-08-31 22:23
---
*** Bug 23657 has been marked as a duplicate of this bug. ***
--
What|Removed |Added
19 matches
Mail list logo