http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45230
--- Comment #17 from t7 at gmail dot com t7 at gmail dot com
2010-10-01 03:24:52 UTC ---
(In reply to comment #16)
Fixed.
sorry you only introduced the problem into another error.
this maybe multiple problems.
what did you fix, which
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45406
t66...@gmail.com t7 at gmail dot com changed:
What|Removed |Added
Status|RESOLVED|UNCONFIRMED
at gcc dot gnu dot org
ReportedBy: t7 at gmail dot com
GCC target triplet: i686-w64-mingw32
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45759
--- Comment #15 from t7 at gmail dot com 2010-09-22 12:20 ---
Hello,
Thank you so much for getting this problem fixed.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45694
--- Comment #11 from t7 at gmail dot com 2010-09-21 10:28 ---
Hi,
(In reply to comment #0)
Hi,
(i first reported this to mingw32-w64's bug tracker:
http://sourceforge.net/tracker/?func=detailaid=3067541group_id=202880atid=983354
and was forwarded here)
Kai has posted a patch
--- Comment #6 from t7 at gmail dot com 2010-09-20 11:41 ---
(In reply to comment #3)
Even simpler testcase, now in C.
#include stdio.h
#include stdlib.h
void a()
{
char s[2];
void b() {
char p[4096];
You deliberately use a very large storage for a very
--- Comment #8 from t7 at gmail dot com 2010-09-20 11:59 ---
(In reply to comment #7)
Hi,
yes the stack size is relevant here, because otherwise gcc does not
call ___chkstk(), which seems to be the trouble here. 4K stack usage
is not very big IMHO.
I went deeper... and found out
--
t7 at gmail dot com changed:
What|Removed |Added
Severity|normal |blocker
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45666
--- Comment #10 from t7 at gmail dot com 2010-09-21 05:57 ---
(In reply to comment #9)
(In reply to comment #8)
This issue is caused by the fact that __chkstk clobbers r10 (see its
constrains), which is used here as argument-register for this nested function.
So something
--- Comment #4 from t7 at gmail dot com 2010-09-19 12:17 ---
2nd ICE from PR45727 show same lto problem.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45448
--- Comment #13 from t7 at gmail dot com 2010-09-20 04:00 ---
Ok this ticket is getting very confusing now and no development recently.
--- Comment #12 From Zdenek Sojka 2010-09-15 18:39 [reply] ---
You are compiling it without graphite and yet you are using graphite
--- Comment #16 from t7 at gmail dot com 2010-09-18 01:04 ---
(In reply to comment #15)
(In reply to comment #14)
Created an attachment (id=21820)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21820action=view) [edit]
testcase for problem
As this test need more
--- Comment #17 from t7 at gmail dot com 2010-09-18 01:14 ---
(In reply to comment #15)
(In reply to comment #14)
Created an attachment (id=21820)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21820action=view) [edit]
testcase for problem
As this test need more
--- Comment #8 from t7 at gmail dot com 2010-09-16 21:58 ---
(In reply to comment #4)
(In reply to comment #2)
http://gcc.gnu.org/bugs/#need
Since this is a bug in the preprocessor it is hard to get a preprocessed
source
that causes a bug.
This is very odd, because I
--- Comment #10 from t7 at gmail dot com 2010-09-16 22:03 ---
Program received signal SIGSEGV, Segmentation fault.
gt_ggc_mx_cpp_macro (x_p=value optimized out) at gtype-desc.c:2078
2078 ((*x).params[i0]) ? HT_IDENT_TO_GCC_IDENT (HT_NODE
(((*x).params[i0]))) : NULL
--- Comment #11 from t7 at gmail dot com 2010-09-16 22:06 ---
But too bad this file 'gtype-desc.c' is automatically generated at build time.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45362
--- Comment #13 from t7 at gmail dot com 2010-09-16 22:33 ---
(In reply to comment #12)
Can you try compiling it with
--param ggc-min-expand=0 --param ggc-min-heapsize=0
? Perhaps you'll trigger it then more reliably...
Without it:
GGC heuristics: --param ggc-min-expand=30
--- Comment #5 from t7 at gmail dot com 2010-09-15 08:56 ---
Peeled this skin (164193) off and then blood comes running out.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45362
--- Comment #2 from t7 at gmail dot com 2010-09-14 21:28 ---
(In reply to comment #1)
*** This bug has been marked as a duplicate of 45362 ***
--
t7 at gmail dot com changed:
What|Removed |Added
--- Comment #8 from t7 at gmail dot com 2010-09-14 22:55 ---
No idea, what is going on but I saved your testcase.c as pr45230 and it doesn't
produce the ICE, target gcc is x86_64-w64-mingw32.
bash-4.1$ ./xmingw-trunk-w64-sjlj/bin/x86_64-w64-mingw32-gcc -w -Os -lm -m32
-fgraphite
--- Comment #10 from t7 at gmail dot com 2010-09-15 00:17 ---
(In reply to comment #9)
ICEs are atill present for both strncmp-1.c and reduced testcase on
x86_64-apple-darwin10 at r164287.
You are right. I was suspicious about the pr45230 having no .c extension in the
file name
--- Comment #11 from t7 at gmail dot com 2010-09-15 00:23 ---
FYI, I applied these to gcc-trunk for testing purposes.
[PATCH 1/6] Factor out is_gimple_reg calls.
[PATCH 2/6] A function is affine when CHREC_RIGHT is invariant.
[PATCH 3/6] Fix chrec_contains_symbols_defined_in_loop
: t7 at gmail dot com
GCC host triplet: x86_64-w64-mingw32
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45666
--- Comment #7 from t7 at gmail dot com 2010-09-10 05:47 ---
Thank you very much for fixing this bug, could you please close this after it
is fixed on trunk ?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45230
--- Comment #4 from t7 at gmail dot com 2010-09-09 00:09 ---
Status?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45406
--- Comment #5 from t7 at gmail dot com 2010-09-09 04:55 ---
What is the status of this PR ?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45230
--- Comment #4 from t7 at gmail dot com 2010-08-26 06:04 ---
*** Bug 45406 has been marked as a duplicate of this bug. ***
--
t7 at gmail dot com changed:
What|Removed |Added
--- Comment #3 from t7 at gmail dot com 2010-08-26 06:04 ---
*** This bug has been marked as a duplicate of 45230 ***
--
t7 at gmail dot com changed:
What|Removed |Added
Version: 4.6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: t7 at gmail dot com
GCC host triplet: x86_64-w64-mingw32
http://gcc.gnu.org/bugzilla/show_bug.cgi?id
--- Comment #1 from t7 at gmail dot com 2010-08-25 15:46 ---
Created an attachment (id=21562)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21562action=view)
testcase
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45405
--- Comment #5 from t7 at gmail dot com 2010-08-25 16:11 ---
Hi,
(In reply to comment #4)
Well. I do not have access to i686-pc-mingw32-gcc and this seems related to
/* Return whether OP is a DECL whose address is function-invariant. */
bool
decl_address_invariant_p
--- Comment #2 from t7 at gmail dot com 2010-08-25 16:11 ---
*** This bug has been marked as a duplicate of 45255 ***
--
t7 at gmail dot com changed:
What|Removed |Added
--- Comment #6 from t7 at gmail dot com 2010-08-25 16:11 ---
*** Bug 45405 has been marked as a duplicate of this bug. ***
--
t7 at gmail dot com changed:
What|Removed |Added
Priority: P3
Component: middle-end
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: t7 at gmail dot com
GCC host triplet: x86_64-w64-mingw32
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45406
--- Comment #1 from t7 at gmail dot com 2010-08-25 16:48 ---
Created an attachment (id=21563)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21563action=view)
testcase
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45406
--- Comment #5 from t7 at gmail dot com 2010-08-24 21:43 ---
Why nobody is attending my ticket ???
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45392
--- Comment #7 from t7 at gmail dot com 2010-08-24 22:47 ---
(From update of attachment 21551)
gz format requested.
--
t7 at gmail dot com changed:
What|Removed |Added
--- Comment #8 from t7 at gmail dot com 2010-08-24 22:47 ---
Created an attachment (id=21558)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21558action=view)
testcase
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45392
--- Comment #9 from t7 at gmail dot com 2010-08-24 22:50 ---
(In reply to comment #6)
(In reply to comment #5)
Why nobody is attending my ticket ???
GCC is mostly volunteer work and some folks have other priorities right now.
Not to mention you compressed the preprocessed
--- Comment #11 from t7 at gmail dot com 2010-08-24 22:56 ---
(In reply to comment #10)
The output of gcc -v will provide with the exact version of GCC that you
used.
gcc version 4.6.0 20100823 (experimental)
163469
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45392
--- Comment #12 from t7 at gmail dot com 2010-08-25 00:14 ---
(In reply to comment #2)
*** This bug has been marked as a duplicate of 44562 ***
You know what, if you don't want to fix it then just mark it won't fix.
Stop marking stuff you don't know and you think
--- Comment #9 from t7 at gmail dot com 2010-08-25 00:37 ---
*** Bug 45392 has been marked as a duplicate of this bug. ***
--
t7 at gmail dot com changed:
What|Removed |Added
--- Comment #14 from t7 at gmail dot com 2010-08-25 00:37 ---
(In reply to comment #13)
(In reply to comment #4)
Both test from pr44562 compiled fine on Windows 7 x64 Native Win64
x86_64-w64-mingw32 Multi-lib 32/64 Bits capable GCC Compiler.
gcc -O1 -flto -fstrict-aliasing
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: t7 at gmail dot com
GCC host triplet: x86_64-w64-mingw32
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45392
--- Comment #1 from t7 at gmail dot com 2010-08-24 01:45 ---
Created an attachment (id=21551)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21551action=view)
reduced testcase
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45392
--- Comment #3 from t7 at gmail dot com 2010-08-24 02:48 ---
Can not re-produce 44562 problem on Windows 7 x64 native gcc-trunk compiler
target=x86_64-w64-mingw32
Compiled fine.
gcc -O1 -flto -fstrict-aliasing -fgraphite-identity pr44562.c
Can't compile on Windows 7 gcc-trunk
--- Comment #4 from t7 at gmail dot com 2010-08-24 02:55 ---
Both test from pr44562 compiled fine on Windows 7 x64 Native Win64
x86_64-w64-mingw32 Multi-lib 32/64 Bits capable GCC Compiler.
gcc -O1 -flto -fstrict-aliasing -fgraphite-identity -c pr44562.c
gcc -O3 -g -fwhopr -c step2
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: t7 at gmail dot com
GCC build triplet: x86_64-w64-mingw32
GCC host triplet: x86_64-slackware-linux
GCC target triplet: x86_64-w64-mingw32
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42768
--- Comment #1 from t7 at gmail dot com 2010-01-16 13:39 ---
Created an attachment (id=19622)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19622action=view)
saves
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42768
--- Comment #2 from t7 at gmail dot com 2010-01-16 21:09 ---
libstdc++-v3/libsupc++/vec.cc: In function 'void __cxxabiv1::T.60(void*,
size_t, size_t, __cxxabiv1::__cxa_cdtor_return_type (*)(void*))':
libstdc++-v3/libsupc++/vec.cc:354: internal compiler error: Segmentation fault
--- Comment #11 from t7 at gmail dot com 2010-01-05 11:14 ---
nothing to do with gcc
--
t7 at gmail dot com changed:
What|Removed |Added
Status
--- Comment #9 from t7 at gmail dot com 2009-12-25 09:18 ---
Most unfortunate the gcc-4.* built with crt and win32api from
http://sf.net/projects/mingw do not suffer from this bug. Therefore specific to
target i686/x86_64-w64-mingw32 http://sourceforge.net/projects/mingw-w64 only
: normal
Priority: P3
Component: rtl-optimization
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: t7 at gmail dot com
GCC build triplet: x86_64-slackware-linux
GCC host triplet: x86_64-slackware-linux
GCC target triplet: x86_64-w64-mingw32
http
--- Comment #1 from t7 at gmail dot com 2009-12-24 11:44 ---
Created an attachment (id=19386)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19386action=view)
saves .ok compiled with -fno-optimize-sibling-calls
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42489
--- Comment #2 from t7 at gmail dot com 2009-12-24 11:57 ---
(gdb) disass $pc-30 $pc+30
Dump of assembler code from 0x4933e3 to 0x49341f:
0x004933e3 __xmlRaiseError+179: add%al,(%eax)
0x004933e5 __xmlRaiseError+181: add%al,%bh
0x004933e7 __xmlRaiseError+183
--- Comment #4 from t7 at gmail dot com 2009-12-24 21:29 ---
(In reply to comment #3)
Some issues with -foptimize-sibling-calls were fixed in GCC 4.5
Backport it to 4.4 branch?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42489
--- Comment #5 from t7 at gmail dot com 2009-12-24 22:09 ---
(In reply to comment #3)
Some issues with -foptimize-sibling-calls were fixed in GCC 4.5
Which revision fix in trunk??
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42489
--- Comment #6 from t7 at gmail dot com 2009-12-24 22:44 ---
Cause endless maximum cpu usage in application run-time.
--
t7 at gmail dot com changed:
What|Removed |Added
: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstrap
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: t7 at gmail dot com
GCC build triplet: x86_64-slackware-linux
GCC host triplet: x86_64-slackware-linux
GCC target triplet
--- Comment #1 from t7 at gmail dot com 2009-12-24 23:52 ---
--with-system-zlib is not default.
--
t7 at gmail dot com changed:
What|Removed |Added
--- Comment #7 from t7 at gmail dot com 2009-12-25 02:46 ---
(In reply to comment #3)
Some issues with -foptimize-sibling-calls were fixed in GCC 4.5
False.
Browsed all recently committed gcc svn change-logs saw no
-foptimize-sibling-calls related fixes.
Updated gcc-trunk svn
--- Comment #8 from t7 at gmail dot com 2009-12-25 02:51 ---
No simple test-case code can be provided you have to read libxml2 source
error.c about less then 1000 lines.
Without running program in the gdb, fprintf to stderr in the beginning of the
__xmlRaiseError
Priority: P3
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: t7 at gmail dot com
GCC build triplet: i486-slackware-linux
GCC host triplet: x86_64-w64-mingw32
GCC target triplet: x86_64-w64-mingw32
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41531
--- Comment #1 from t7 at gmail dot com 2009-10-01 06:50 ---
Created an attachment (id=18684)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18684action=view)
Preprocessed test case.
gcc version 4.5.0 20090928 Revision 152257
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id
--- Comment #14 from t7 at gmail dot com 2009-09-21 11:05 ---
I can confirm this is fixed in gcc-4_4-branch.
Thank you.
--
t7 at gmail dot com changed:
What|Removed |Added
at gcc dot gnu dot org
ReportedBy: t7 at gmail dot com
GCC build triplet: i486-slackware-linux
GCC host triplet: x86_64-w64-mingw32
GCC target triplet: x86_64-w64-mingw32
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41406
--- Comment #1 from t7 at gmail dot com 2009-09-19 11:55 ---
Created an attachment (id=18607)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18607action=view)
Preprocessed test case.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41406
--- Comment #3 from t7 at gmail dot com 2009-09-19 23:25 ---
(In reply to comment #2)
What version of gcc do you use?
I cannot reproduce the error on amd64-linux with the current trunk at
rev.151881.
I used the cross compiler I compiled from gcc trunk svn revision 151878
--- Comment #13 from t7 at gmail dot com 2009-09-18 09:11 ---
Hmm I haven't noticed this bug has been fixed a week ago, since [Revision
151627], it was still reproducible at [Revision 151584] which was just a day
before.
Thanks!!
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id
--- Comment #31 from t7 at gmail dot com 2009-09-09 09:08 ---
Sorry about the delayed testing.
With the same gcc revision (without patch applied) and with
-Wl,--stack=0x2000 as suggested by Danny.
cc1plus.exe still crashed while running the following command.
g++ -c -include
--- Comment #8 from t7 at gmail dot com 2009-09-08 06:24 ---
ccache x86_64-w64-mingw32-gcc -DHAVE_AV_CONFIG_H -I.
-I/home/slack/vlc/x86_64/ffmpeg
-I/home/slack/local/xmingw-4.5-trunk-w64-sjlj/x86_64-w64-mingw32/include/directx
-I/home/slack/local/k8-sse3-master/w64-xmingw-4.5-trunk
--- Comment #10 from t7 at gmail dot com 2009-09-08 22:31 ---
Created an attachment (id=18550)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18550action=view)
Preprocessed test case.
Sorry about that forgot to remove ccache that's why.
--
t7 at gmail dot com changed
--- Comment #5 from t7 at gmail dot com 2009-09-07 10:03 ---
(In reply to comment #4)
Please attach the .i (preprocessed) source file so that I can duplicate the
problem. Thanks in advance,
I'd like to do that, but, I can not find the .i file all I saw was the .s file
--- Comment #6 from t7 at gmail dot com 2009-09-07 10:05 ---
with -O0 (gcc didn't ICE) libavformat-oggparseogm-s.tar.bz2
with -O3 oggparseog.ICE.s
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41289
--- Comment #1 from t7 at gmail dot com 2009-09-07 23:46 ---
Just found out yesterday afternoon that the binary dll does work correctly.
--
t7 at gmail dot com changed:
What|Removed |Added
--- Comment #13 from t7 at gmail dot com 2009-09-06 12:55 ---
(In reply to comment #12)
Created an attachment (id=18516)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18516action=view) [edit]
patch
here it is
Confirm fixed.
--
http://gcc.gnu.org/bugzilla
--- Comment #14 from t7 at gmail dot com 2009-09-06 13:57 ---
(In reply to comment #12)
Created an attachment (id=18516)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18516action=view) [edit]
patch
here it is
For some reason this leads to :
Problem signature:
Problem
--- Comment #15 from t7 at gmail dot com 2009-09-06 13:59 ---
(gdb) print $pc
$1 = (void (*)()) 0x80e132 QString::at(int) const+26
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41254
--- Comment #18 from t7 at gmail dot com 2009-09-06 21:59 ---
(In reply to comment #17)
The patch bootstrapped and tested ok but I'm holding off until you confirm
it's
not the reason for the issue you see.
I can confirm, that indeed patch fixed this bug.
Yes patch bootstrapped
--- Comment #20 from t7 at gmail dot com 2009-09-06 22:14 ---
(In reply to comment #16)
Try building without the patch but with unlimited stack (ulimit -s unlimited)
and see if the same error appears.
Actually can't try this because I'm using the native compiler to build qt4
--- Comment #22 from t7 at gmail dot com 2009-09-06 22:20 ---
(In reply to comment #16)
Try building without the patch but with unlimited stack (ulimit -s unlimited)
and see if the same error appears.
You mean cross compile the native compiler from linux by setting the shell
--- Comment #23 from t7 at gmail dot com 2009-09-06 22:21 ---
(In reply to comment #16)
Try building without the patch but with unlimited stack (ulimit -s unlimited)
and see if the same error appears.
This is under MSys/Mingw shell
$ ulimit -s unlimited
sh: ulimit: stack size
--- Comment #25 from t7 at gmail dot com 2009-09-06 22:27 ---
(In reply to comment #21)
Yes, that could be the reason. Can you test the same revision without the
patch again?
Ok there maybe a reason for qmake.exe crash, during the process, I changed the
O flag for building
--- Comment #26 from t7 at gmail dot com 2009-09-06 22:30 ---
(In reply to comment #24)
Just the same way as you reported the bug (I understand that this
was a native compiler issue?). There surely must be a way to increase
the maximum stack size with windows?
Yes
--- Comment #27 from t7 at gmail dot com 2009-09-06 22:41 ---
Ok I just found out that it is the -O and up causing the problem, I just
changed script back to -O0 and it compiles and runs fine, right now up to
corelib.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41254
--- Comment #28 from t7 at gmail dot com 2009-09-06 22:43 ---
Thank you for the help, this bug can be close.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41254
--- Comment #29 from t7 at gmail dot com 2009-09-06 22:55 ---
Confirmed that qt4 library build was complete with -O0.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41254
Version: 4.5.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: t7 at gmail dot com
GCC build triplet: i486-slackware-linux
GCC host triplet: x86_64-w64-mingw32
--- Comment #1 from t7 at gmail dot com 2009-09-07 02:39 ---
Created an attachment (id=18521)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18521action=view)
tmp .saves
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41289
--- Comment #2 from t7 at gmail dot com 2009-09-07 03:04 ---
Created an attachment (id=18522)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18522action=view)
saves
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41289
--- Comment #3 from t7 at gmail dot com 2009-09-05 07:02 ---
(In reply to comment #2)
The preprocessed source is not useful as it contains references to the
precompiled header. Please reproduce without the precompiled header.
I have no idea on how to do that I would like
--- Comment #5 from t7 at gmail dot com 2009-09-05 10:53 ---
Created an attachment (id=18503)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18503action=view)
Preprocessed test case.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41254
--- Comment #11 from t7 at gmail dot com 2009-09-06 00:03 ---
I can test the patch.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41254
dot gnu dot org
ReportedBy: t7 at gmail dot com
GCC build triplet: x86_64-w64-mingw32
GCC host triplet: x86_64-w64-mingw32
GCC target triplet: x86_64-w64-mingw32
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41207
--- Comment #4 from t7 at gmail dot com 2009-08-31 11:08 ---
g++ --save-temps -c -omain.o -O -I. -Igenerators -Igenerators/unix
-Igenerators/win32 -Igenerators/mac
-IE:\msys\1.0\qt-all-opensource-src-4.5.2/include
-IE:\msys\1.0\qt-all-opensource-src-4.5.2/include/QtCore
-IE:\msys
--- Comment #5 from t7 at gmail dot com 2009-08-31 11:15 ---
Created an attachment (id=18454)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18454action=view)
Preprocessed test case.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41153
--- Comment #6 from t7 at gmail dot com 2009-08-31 11:16 ---
Created an attachment (id=18455)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18455action=view)
saves
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41153
--- Comment #3 from t7 at gmail dot com 2009-08-30 09:43 ---
Only encountered with c++ code.
--
t7 at gmail dot com changed:
What|Removed |Added
GCC build
ReportedBy: t7 at gmail dot com
GCC host triplet: x86_64
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41153
--- Comment #2 from t7 at gmail dot com 2009-08-21 10:36 ---
Hello,
I can confirm this issue have been solved by mingw-w64 (updating mingw-w64-crt)
in the latest source in svn repository
(http://sourceforge.net/projects/mingw-w64/develop).
---
sezero committed revision 1181
1 - 100 of 102 matches
Mail list logo