[Bug driver/39356] assembler isn't called

2009-09-01 Thread ktietz at gcc dot gnu dot org
--- Comment #19 from ktietz at gcc dot gnu dot org 2009-09-01 16:16 --- I verified it by myself and it is a duplicate of 41184 *** This bug has been marked as a duplicate of 41184 *** -- ktietz at gcc dot gnu dot org changed: What|Removed |Added

[Bug driver/39356] assembler isn't called

2009-08-31 Thread rainer at emrich-ebersheim dot de
--- Comment #18 from rainer at emrich-ebersheim dot de 2009-08-31 08:11 --- Subject: Re: assembler isn't called -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 ktietz at gcc dot gnu dot org schrieb: --- Comment #17 from ktietz at gcc dot gnu dot org 2009-08-30 08:35 ---

[Bug driver/39356] assembler isn't called

2009-08-30 Thread ktietz at gcc dot gnu dot org
--- Comment #17 from ktietz at gcc dot gnu dot org 2009-08-30 08:35 --- (In reply to comment #16) (In reply to comment #15) Is there a chance that we get this fixed soon? Rainer Well, I would like to fix this. Better now then later. But I couldn't find the real reason for

[Bug driver/39356] assembler isn't called

2009-07-22 Thread rainer at emrich-ebersheim dot de
--- Comment #15 from rainer at emrich-ebersheim dot de 2009-07-22 12:24 --- Is there a chance that we get this fixed soon? Rainer -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39356

[Bug driver/39356] assembler isn't called

2009-07-22 Thread ktietz at gcc dot gnu dot org
--- Comment #16 from ktietz at gcc dot gnu dot org 2009-07-22 16:06 --- (In reply to comment #15) Is there a chance that we get this fixed soon? Rainer Well, I would like to fix this. Better now then later. But I couldn't find the real reason for this issue. The patch above

[Bug driver/39356] assembler isn't called

2009-06-21 Thread xenofears at gmail dot com
--- Comment #12 from xenofears at gmail dot com 2009-06-22 01:11 --- (In reply to comment #10) (In reply to comment #9) Patch sent. See http://gcc.gnu.org/ml/gcc-patches/2009-03/msg00914.html (I am new as an official team member of Mingw-w64, and am making a project of my own based

[Bug driver/39356] assembler isn't called

2009-06-21 Thread pinskia at gcc dot gnu dot org
--- Comment #13 from pinskia at gcc dot gnu dot org 2009-06-22 01:42 --- *** Bug 40513 has been marked as a duplicate of this bug. *** -- pinskia at gcc dot gnu dot org changed: What|Removed |Added

[Bug driver/39356] assembler isn't called

2009-06-21 Thread pinskia at gcc dot gnu dot org
--- Comment #14 from pinskia at gcc dot gnu dot org 2009-06-22 01:42 --- *** Bug 40514 has been marked as a duplicate of this bug. *** -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39356

[Bug driver/39356] assembler isn't called

2009-03-19 Thread nightstrike at gmail dot com
--- Comment #11 from nightstrike at gmail dot com 2009-03-20 05:28 --- I can confirm that our 4.3 release worked, and that this is a 4.4 regression. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39356

[Bug driver/39356] assembler isn't called

2009-03-16 Thread ktietz at gcc dot gnu dot org
--- Comment #9 from ktietz at gcc dot gnu dot org 2009-03-16 09:15 --- (In reply to comment #8) (In reply to comment #7) The following patch solves this problem and prevents the name collision for 32 and 64 bits win32 systems. ChangeLog * config/i386/i386.md

[Bug driver/39356] assembler isn't called

2009-03-15 Thread ktietz at gcc dot gnu dot org
--- Comment #6 from ktietz at gcc dot gnu dot org 2009-03-15 20:08 --- This bug was reasoned by duplicate existance of function __chkstk. For targets mingw/cygwin this symbol allocates and probes stack (see /gcc/config/i386/cygwin.asm). The VC variant export the same symbol name in

[Bug driver/39356] assembler isn't called

2009-03-15 Thread ktietz at gcc dot gnu dot org
--- Comment #7 from ktietz at gcc dot gnu dot org 2009-03-15 20:13 --- The following patch solves this problem and prevents the name collision for 32 and 64 bits win32 systems. ChangeLog * config/i386/i386.md (allocate_stack_worker_32): Use ___gnu_chkstk.

[Bug driver/39356] assembler isn't called

2009-03-15 Thread dannysmith at users dot sourceforge dot net
--- Comment #8 from dannysmith at users dot sourceforge dot net 2009-03-16 02:13 --- (In reply to comment #7) The following patch solves this problem and prevents the name collision for 32 and 64 bits win32 systems. ChangeLog * config/i386/i386.md

[Bug driver/39356] assembler isn't called

2009-03-09 Thread r dot emrich at de dot tecosim dot com
--- Comment #5 from r dot emrich at de dot tecosim dot com 2009-03-09 15:07 --- (In reply to comment #4) Sorry, pex_run co aren't the reason for this issue. By further debugging I found that for bigger functions using alloca with variable sizes wrong code is generated for

[Bug driver/39356] assembler isn't called

2009-03-07 Thread ktietz at gcc dot gnu dot org
--- Comment #4 from ktietz at gcc dot gnu dot org 2009-03-07 10:46 --- (In reply to comment #3) Well, the issues in driver seems to be related to pexecute in protoize.c. On a first glance, I noticed that here for pid's an 'int' type is used (btw in libiberty a 'long' is used for

[Bug driver/39356] assembler isn't called

2009-03-06 Thread ktietz at gcc dot gnu dot org
--- Comment #3 from ktietz at gcc dot gnu dot org 2009-03-06 15:12 --- Well, the issues in driver seems to be related to pexecute in protoize.c. On a first glance, I noticed that here for pid's an 'int' type is used (btw in libiberty a 'long' is used for keeping the pids, which is for

[Bug driver/39356] assembler isn't called

2009-03-04 Thread r dot emrich at de dot tecosim dot com
--- Comment #2 from r dot emrich at de dot tecosim dot com 2009-03-04 09:07 --- (In reply to comment #1) Huh. It's not even compiling. You're right. OTOH the sequence $ gcc -v -S hello.c $ gcc -v -c hello.s $ gcc -v -o hello hello.o builds correctly. Anyway the driver is broken

[Bug driver/39356] assembler isn't called

2009-03-03 Thread rguenth at gcc dot gnu dot org
--- Comment #1 from rguenth at gcc dot gnu dot org 2009-03-03 16:57 --- Huh. It's not even compiling. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39356