public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vasco at icpnet dot pl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/48649] cannot find space to spill in GENERAL REGISTERS
Date: Sun, 25 Mar 2012 15:50:00 -0000	[thread overview]
Message-ID: <bug-48649-4-QworfNhnqG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48649-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48649

Popielewicz <vasco at icpnet dot pl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|4.3.5                       |4.3.6

--- Comment #7 from Popielewicz <vasco at icpnet dot pl> 2012-03-25 15:37:46 UTC ---
(In reply to comment #6)
> OK.
> Because I suspected, that IRA could help I have decided to port 4.4.6, the last
> with coff.
> Another motivation was tree-vectorizer.
> 
>

In the meantime I have fixed gmp lib and values of limits as those met in
limits.h or glimits.h etc.  Now it seems gcc-4.4.6 compiles and links correctly
even big packages. It is too soon to say it is rock stable but it is usable.
The conclusion is coff support in gcc was probably to the end in good shape.
It is a pity it was obsoleted.

I think the case can be closed.

Andrzej


  parent reply	other threads:[~2012-03-25 15:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-17 11:08 [Bug c/48649] New: " vasco at icpnet dot pl
2011-04-17 11:18 ` [Bug c/48649] " vasco at icpnet dot pl
2011-04-17 11:42 ` vasco at icpnet dot pl
2011-04-17 12:29 ` vasco at icpnet dot pl
2011-04-17 16:17 ` vasco at icpnet dot pl
2011-04-18 10:36 ` [Bug target/48649] " rguenth at gcc dot gnu.org
2011-10-18  7:25 ` vasco at icpnet dot pl
2012-03-25 15:50 ` vasco at icpnet dot pl [this message]
2021-12-08 18:11 ` pinskia at gcc dot gnu.org
2021-12-08 18:16 ` pinskia at gcc dot gnu.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=bug-48649-4-QworfNhnqG@http.gcc.gnu.org/bugzilla/ \
    --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).