public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ktietz at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/39356] assembler isn't called
Date: Sat, 07 Mar 2009 10:46:00 -0000 [thread overview]
Message-ID: <20090307104603.13592.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39356-11564@http.gcc.gnu.org/bugzilla/>
------- 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 keeping the pids, which is for w64 incorrect,
> too).
> The problem is, that pid_t has to have a scalar size on w64 of 64-bits.
>
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 optimizations bigger then -O0.
By this reason the driver gcc.c in execute is broken. The interesting issue
about this is, when trying to make a smaller testcase out of it, code is
produced correct.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39356
next prev parent reply other threads:[~2009-03-07 10:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 14:03 [Bug driver/39356] New: " r dot emrich at de dot tecosim dot com
2009-03-03 16:57 ` [Bug driver/39356] " rguenth at gcc dot gnu dot org
2009-03-04 9:07 ` r dot emrich at de dot tecosim dot com
2009-03-06 15:12 ` ktietz at gcc dot gnu dot org
2009-03-07 10:46 ` ktietz at gcc dot gnu dot org [this message]
2009-03-09 15:07 ` r dot emrich at de dot tecosim dot com
2009-03-15 20:08 ` ktietz at gcc dot gnu dot org
2009-03-15 20:13 ` ktietz at gcc dot gnu dot org
2009-03-16 2:13 ` dannysmith at users dot sourceforge dot net
2009-03-16 9:16 ` ktietz at gcc dot gnu dot org
2009-03-19 14:33 ` ktietz at gcc dot gnu dot org
2009-03-20 5:29 ` nightstrike at gmail dot com
2009-06-22 1:11 ` xenofears at gmail dot com
2009-06-22 1:42 ` pinskia at gcc dot gnu dot org
2009-06-22 1:43 ` pinskia at gcc dot gnu dot org
2009-07-22 12:24 ` rainer at emrich-ebersheim dot de
2009-07-22 16:07 ` ktietz at gcc dot gnu dot org
2009-08-30 8:35 ` ktietz at gcc dot gnu dot org
2009-08-31 8:11 ` rainer at emrich-ebersheim dot de
2009-09-01 16:16 ` ktietz at gcc dot gnu dot org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090307104603.13592.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).