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 c++/35159] g++ and gfortran inoperable with no error message
Date: Wed, 24 Jun 2009 10:28:00 -0000 [thread overview]
Message-ID: <20090624102806.3028.qmail@sourceware.org> (raw)
In-Reply-To: <bug-35159-14772@http.gcc.gnu.org/bugzilla/>
------- Comment #25 from ktietz at gcc dot gnu dot org 2009-06-24 10:28 -------
This bug was fixed for 4.4 version. The real issue here was the changes happend
to ira and specifying one register via the constrains "=a" or "+a". Both
variant don't work anymore. By expanding the stack_allocator methods (for
32-bit and 64-bit) by one input and one output contrain, it solves the issue.
--
ktietz at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution| |FIXED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35159
prev parent reply other threads:[~2009-06-24 10:28 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 7:38 [Bug c++/35159] New: g++ " nightstrike at gmail dot com
2008-02-11 7:40 ` [Bug c++/35159] " nightstrike at gmail dot com
2008-02-11 14:52 ` rguenth at gcc dot gnu dot org
2008-02-11 14:57 ` ktietz at gcc dot gnu dot org
2008-02-14 1:54 ` nightstrike at gmail dot com
2008-02-14 7:00 ` mmitchel at gcc dot gnu dot org
2008-02-14 8:16 ` jakub at gcc dot gnu dot org
2008-02-14 9:08 ` ktietz at gcc dot gnu dot org
2008-02-14 9:19 ` ubizjak at gmail dot com
2008-02-14 9:27 ` ktietz at gcc dot gnu dot org
2008-02-14 9:33 ` rguenth at gcc dot gnu dot org
2008-02-14 9:39 ` ubizjak at gmail dot com
2008-02-14 10:04 ` ktietz at gcc dot gnu dot org
2008-02-14 14:28 ` nightstrike at gmail dot com
2008-02-14 14:29 ` nightstrike at gmail dot com
2008-02-16 17:23 ` [Bug c++/35159] g++ and gfortran " nightstrike at gmail dot com
2008-02-16 19:51 ` ktietz at gcc dot gnu dot org
2008-03-06 3:01 ` nightstrike at gmail dot com
2008-03-06 4:51 ` jvdelisle at gcc dot gnu dot org
2008-03-06 5:10 ` nightstrike at gmail dot com
2008-03-06 16:09 ` nightstrike at gmail dot com
2008-03-08 6:06 ` jvdelisle at gcc dot gnu dot org
2008-05-13 13:24 ` nightstrike at gmail dot com
2008-09-21 15:03 ` pepalogik at seznam dot cz
2008-09-21 17:08 ` nightstrike at gmail dot com
2008-10-20 11:25 ` ktietz at gcc dot gnu dot org
2009-06-24 10:28 ` ktietz at gcc dot gnu dot org [this message]
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=20090624102806.3028.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).