public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dave at hiauly1 dot hia dot nrc dot ca" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/32398] [4.3 Regression] checking for suffix of object files... configure: error: cannot compute suffix of f object files: cannot compile
Date: Sat, 07 Jul 2007 23:30:00 -0000	[thread overview]
Message-ID: <20070707233050.24165.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32398-276@http.gcc.gnu.org/bugzilla/>



------- Comment #10 from dave at hiauly1 dot hia dot nrc dot ca  2007-07-07 23:30 -------
Subject: Re:  [4.3 Regression] checking for suffix of object files...
configure: error: cannot compute suffix of f obje

> suggest a way that we could accommodate this?

Prior to reload being completed, I don't see that it matters whether
the argument pointer is fixed or not.  See df_get_entry_block_def_set().
After reload, I believe that we also need to mark the register in
entry_block_defs.

There may be refinements to this depending on whether the argument
pointer is used or not.  This might improve register allocation.
The argument pointer is always copied when it isn't fixed.  See
default_internal_arg_pointer().

For now, I would suggest being conservative.  For example, we aren't
fussy as to whether argument registers are actually used or not.

Dave


-- 


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


  parent reply	other threads:[~2007-07-07 23:30 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-19  2:00 [Bug regression/32398] New: " danglin at gcc dot gnu dot org
2007-06-19  2:39 ` [Bug regression/32398] " danglin at gcc dot gnu dot org
2007-06-21 23:09 ` [Bug regression/32398] [4.3 Regression] " pinskia at gcc dot gnu dot org
2007-06-21 23:49 ` danglin at gcc dot gnu dot org
2007-06-29 18:48 ` mmitchel at gcc dot gnu dot org
2007-07-02 18:12 ` danglin at gcc dot gnu dot org
2007-07-02 18:17 ` [Bug middle-end/32398] " pinskia at gcc dot gnu dot org
2007-07-02 20:08 ` dave at hiauly1 dot hia dot nrc dot ca
2007-07-02 20:23 ` pinskia at gcc dot gnu dot org
2007-07-07 20:30 ` danglin at gcc dot gnu dot org
2007-07-07 22:02 ` dave at hiauly1 dot hia dot nrc dot ca
2007-07-07 22:41 ` zadeck at naturalbridge dot com
2007-07-07 23:30 ` dave at hiauly1 dot hia dot nrc dot ca [this message]
2007-07-08  0:58 ` zadeck at naturalbridge dot com
2007-07-08  2:30 ` dave at hiauly1 dot hia dot nrc dot ca
2007-07-08  2:41 ` zadeck at naturalbridge dot com
2007-07-08  5:12 ` dave at hiauly1 dot hia dot nrc dot ca
2007-07-09 16:31 ` bonzini at gnu dot org
2007-07-09 21:04 ` bonzini at gnu dot org
2007-07-09 22:02 ` dave at hiauly1 dot hia dot nrc dot ca
2007-07-09 22:28 ` zadeck at naturalbridge dot com
2007-07-10  0:04 ` dave at hiauly1 dot hia dot nrc dot ca
2007-07-15 17:19 ` danglin at gcc dot gnu dot org
2007-07-15 17:23 ` danglin 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=20070707233050.24165.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).