public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: palpar <palparni@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Some GCC porting questions
Date: Tue, 27 Oct 2009 03:45:00 -0000	[thread overview]
Message-ID: <mcrocntn3bk.fsf@dhcp-172-17-9-151.mtv.corp.google.com> (raw)
In-Reply-To: <ee737b120910260907y1ffa46eet4f6daa710e58f00a@mail.gmail.com> (palpar's message of "Mon\, 26 Oct 2009 18\:07\:55 +0200")

palpar <palparni@gmail.com> writes:

> 1. How can I tell from the RTL declaration of a function if it is
> declared INLINE of not?

You have to look at the tree decl, at DECL_DECLARED_INLINE_P.

> 2. Where is the code responsible for allocating those variables on the
> stack which don't fit in registers (needed to fix debug info
> generation)?

Look for calls to assign_stack_temp, assign_temp, and friends.

Ian

      reply	other threads:[~2009-10-26 23:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-26 16:37 palpar
2009-10-27  3:45 ` Ian Lance Taylor [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=mcrocntn3bk.fsf@dhcp-172-17-9-151.mtv.corp.google.com \
    --to=iant@google.com \
    --cc=gcc@gcc.gnu.org \
    --cc=palparni@gmail.com \
    /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).