http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53477
asmwarrior changed:
What|Removed |Added
CC||asmwarrior at gmail dot com
--- Comment #3
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53477
--- Comment #4 from asmwarrior ---
This is what I get when I enable the python stack print:
> set python print-stack full
[debug]> set python print-stack full
[debug]>>cb_gdb:
> p m_Headers
[debug]> p m_Headers
[debug]Traceback (most recen
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53477
--- Comment #5 from asmwarrior ---
> p /r m_Headers
[debug]> p /r m_Headers
[debug]$5 = (StringSet &) @0x116d0bc4: {_M_t = {_M_impl =
{ >> =
{<__gnu_cxx::new_allocator >> = {}, }, _M_key_compare = {> = {}, }, _M_header = {_M_color
= std::_S_red,
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53477
--- Comment #6 from asmwarrior ---
Hi, all, I create a simple c++ program to reproduce this bug:
#include
#include
typedef std::set IntSet;
typedef std::map IntToSetMap;
int main()
{
IntToSetMap m;
IntSet s;
s.insert(5);
m[3]
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53477
--- Comment #7 from asmwarrior ---
Ok, I found another issue on the line "return 0", see the GDB log:
[debug]> p m
[debug]$2 = std::map with 1 elements = {[3] = std::set with 2 elements = {[0] =
5, [1] = 6}}
[debug]>>cb_gdb:
[debug]> p m[3]
[
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49951
--- Comment #5 from asmwarrior 2011-10-29
14:06:53 UTC ---
Hi, all, I think this bug happened about more than one years, I have test in
both gcc 4.5 and gcc 4.6.x under Windows.
I have both post an issue in GDB maillist and GCC-help maillist. se
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48914
--- Comment #4 from asmwarrior 2012-08-02
06:41:33 UTC ---
We are Code::Blocks' developers, we see the same annoying warnings, hope it
will be fixed. Thanks.
See:
http://forums.codeblocks.org/index.php/topic,16670.msg113169.html#msg113169
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48914
--- Comment #5 from asmwarrior 2012-08-02
08:28:10 UTC ---
(In reply to comment #4)
> We are Code::Blocks' developers, we see the same annoying warnings, hope it
> will be fixed. Thanks.
> See:
> http://forums.codeblocks.org/index.php/topic,16670
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52602
Bug #: 52602
Summary: false compilation warning of uninitialized variable
Classification: Unclassified
Product: gcc
Version: 4.6.3
Status: UNCONFIRMED
Severity: normal
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52602
--- Comment #1 from asmwarrior 2012-03-16
14:06:08 UTC ---
BTW: here is the discussion in gdb's patch mail list.
http://sourceware.org/ml/gdb-patches/2012-03/msg00585.html
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56926
asmwarrior changed:
What|Removed |Added
CC||asmwarrior at gmail dot com
--- Comment #3
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56926
--- Comment #4 from asmwarrior ---
There is a test case in this post:
http://sourceforge.net/p/mingwbuilds/mailman/message/29214215/
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49951
--- Comment #19 from asmwarrior ---
Hi, I see this bug happens at least in GCC 4.8.2 again. I'm using MinGW-Build
GCC 4.8.2 under Windows, and debug Codeblocks. I have a source code which have
something like:
void CompilerGCC::SetupEnvironment()
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49951
--- Comment #20 from asmwarrior ---
Hi, all. After the conversation on GDB IRC with GDB developer Jan Kratochvil, a
simple test code supplied by Jan in his bug report on
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58123#c0 can easily demonstrate
t
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58123
asmwarrior changed:
What|Removed |Added
CC||asmwarrior at gmail dot com
--- Comment #3
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56926
--- Comment #6 from asmwarrior ---
It is very simple to reproduce this bug. Here is the steps I do
1, download the GCC 4.8.2 from MinGW-w64 site, I'm using
i686-4.8.2-release-posix-dwarf-rt_v3-rev1
2, download the boost source package, I'm using
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49951
--- Comment #14 from asmwarrior 2011-12-21
03:21:07 UTC ---
Thanks for fix this bug, I hope some devs will backport this patch to 4.5/4.6
branches.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71867
--- Comment #12 from asmwarrior ---
Hi, (In reply to Jonathan Wakely from comment #11)
> Does this code still get miscompiled with GCC 6 and newer?
Hi, I'm now using mingw-build i686-7.2.0-release-posix-dwarf-rt_v5-rev1, which
was downloaded fro
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71867
--- Comment #9 from asmwarrior ---
I see this crash issue again, but still it happens in another place of the wx's
source code, add the
__attribute__((optimize("O0")))
To the function which cause the crash can workaround this issue. Note that t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71867
--- Comment #10 from asmwarrior ---
Is it related to pointer casting? I see this post:
https://stackoverflow.com/questions/36816363/gcc-4-9-3-more-aggressive-null-pointer-check-removal
Some one reported that the Null check was removed in the fol
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59474
asmwarrior changed:
What|Removed |Added
CC||asmwarrior at gmail dot com
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56926
--- Comment #11 from asmwarrior ---
Today, I did the same test as in comment 6 with a more recent gcc
5.1(http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/dongsheng-daily/5.x/gcc-5-win32_5.1.1-2015
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56926
--- Comment #12 from asmwarrior ---
Hi, I just did a test on the cygwin 32bit tool chain.
1, download the cygwin installer.
2, install gcc-g++ 4.9.2 and boost 1.57 package
3, run the steps in comment 6, except that you don't need to add the
"-ID
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56926
--- Comment #13 from asmwarrior ---
I did some further test with the condition I stated in comment 11. That is gcc
5.1.
Now, I have pch.h.gch file (about 200M) already generated.
First thing, I try to see whether preprocessor works OK, so I add t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56926
--- Comment #14 from asmwarrior ---
The bug can be seen when "-E" and "-fpch-preprocess" is used together to
generate a preprocessed file.
If I have a small pch file named "spch.h" and "spch.h.gch"(note the spch.h.gch
size is about 47M), and if I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=14940
asmwarrior changed:
What|Removed |Added
CC||asmwarrior at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56926
--- Comment #15 from asmwarrior ---
I think the bug has already reported more than ten years ago, see:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=14940
There are many fixes in various hosts, but not included the windows hosts. As
Kai suggest i
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56926
--- Comment #16 from asmwarrior ---
I think I may find some hard coded which limit the pch file size, it is located
in: gcc/config/i386/host-mingw32.c
You can view the file in
https://gcc.gnu.org/git/?p=gcc.git;a=blob_plain;f=gcc/config/i386/hos
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56926
--- Comment #17 from asmwarrior ---
Good news, I can definitely confirm that enlarge the value: pch_VA_max_size can
solve the crash issue.
Luckily, the value is defined in host-mingw32.c is a const value:
static const size_t pch_VA_max_size = 1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49951
--- Comment #21 from asmwarrior ---
I just test the sample code in comment 20 with GCC 4.9.2, and I see this
"jumpy" behaviour still exists, do we need to reopen this bug? Thanks.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58123
--- Comment #10 from asmwarrior ---
(In reply to Jan Kratochvil from comment #8)
> (In reply to Aldy Hernandez from comment #7)
> > Putting this aside for a second, my question is, do we really want a
> > debugging experience where we jump from b
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56926
--- Comment #19 from asmwarrior ---
Martin Richter has post a patch to solve this issue, see: [Comment
47](https://gcc.gnu.org/bugzilla/show_bug.cgi?id=14940#c47), also there are
some discussion in [MinGW-w64 - for 32 and 64 bit Windows / Bugs /
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=14940
--- Comment #48 from asmwarrior ---
Hi, Martin Richter, thanks, I have post this patch link in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56926.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71867
asmwarrior changed:
What|Removed |Added
CC||asmwarrior at gmail dot com
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71867
--- Comment #4 from asmwarrior ---
It looks like the code is called from an inline function, you can see this code
snippet in the prepossessed file.
inline wxObject *wxCheckDynamicCast(wxObject *obj, wxClassInfo *classInfo)
{
return obj &&
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71867
--- Comment #7 from asmwarrior ---
The -fno-delete-null-pointer-checks option exists in -O2 mode in both GCC 4.9
and GCC 5.x, but this crash issue only happens on GCC 5.x serials. So, why do
you think it is the reason?
See my related discussion
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71867
--- Comment #8 from asmwarrior ---
Hi, I just build wx2.8.12 under TDM-GCC 5.1 with
-fno-delete-null-pointer-checks enabled. But the bad thing is that I still see
the same crash here. The whole command is below:
mingw32-make -f makefile.gcc USE_
37 matches
Mail list logo
