All of lore.kernel.org
 help / color / mirror / Atom feed
From: JiveTalkin <aijazbaig1@gmail.com>
To: linuxppc-dev@ozlabs.org
Subject: Re: ABI defined register usage within function calls
Date: Mon, 15 Jul 2013 17:37:03 -0700 (PDT)	[thread overview]
Message-ID: <CAHB2L+dbwNt8GxMYAvzZO-+WhOOuM_pyjq5XdSJ9Wm_=jHdoKw@mail.gmail.com> (raw)
In-Reply-To: <1373840376.19894.274.camel@pasglop>

[-- Attachment #1: Type: text/plain, Size: 2432 bytes --]

Hi Ben.

Thanks for the information. Your reply is eagerly awaited.

Regards.
On Jul 15, 2013 3:50 AM, "Benjamin Herrenschmidt [via linuxppc]" <
ml-node+s10917n73731h5@n7.nabble.com> wrote:

> On Fri, 2013-07-12 at 04:38 -0700, JiveTalkin wrote:
> > Moderator..can you change the subject of this to "Understanding register
> > usage as per ABI rules for functions" ??
> >
> > Additionally, doesn't anyone have anything to say about this?
>
> We don't modify subjects after the fact. As to why nobody replied, well,
> I suppose the 2 or 3 people who actually understand that stuff were
> all too busy or didn't notice :-)
>
> I'll try to reply later today if I get a chance or you can try to catch
> me on IRC (freenode/#mklinux)
>
> Cheers,
> Ben.
>
> > --
> > View this message in context:
> http://linuxppc.10917.n7.nabble.com/ABI-defined-register-usage-within-function-calls-tp73565p73669.html
> > Sent from the linuxppc-dev mailing list archive at Nabble.com.
> > _______________________________________________
> > Linuxppc-dev mailing list
> > [hidden email] <http://user/SendEmail.jtp?type=node&node=73731&i=0>
> > https://lists.ozlabs.org/listinfo/linuxppc-dev
>
>
> _______________________________________________
> Linuxppc-dev mailing list
> [hidden email] <http://user/SendEmail.jtp?type=node&node=73731&i=1>
> https://lists.ozlabs.org/listinfo/linuxppc-dev
>
>
> ------------------------------
>  If you reply to this email, your message will be added to the discussion
> below:
>
> http://linuxppc.10917.n7.nabble.com/ABI-defined-register-usage-within-function-calls-tp73565p73731.html
>  To unsubscribe from ABI defined register usage within function calls, click
> here<http://linuxppc.10917.n7.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=73565&code=YWlqYXpiYWlnMUBnbWFpbC5jb218NzM1NjV8MTg5MDM1OTIxOA==>
> .
> NAML<http://linuxppc.10917.n7.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>




--
View this message in context: http://linuxppc.10917.n7.nabble.com/ABI-defined-register-usage-within-function-calls-tp73565p73803.html
Sent from the linuxppc-dev mailing list archive at Nabble.com.

[-- Attachment #2: Type: text/html, Size: 4008 bytes --]

  reply	other threads:[~2013-07-16  0:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-10 13:54 ABI defined register usage within function calls JiveTalkin
2013-07-12 11:38 ` JiveTalkin
2013-07-14 22:19   ` Benjamin Herrenschmidt
2013-07-16  0:37     ` JiveTalkin [this message]
2013-07-19 23:49 ` Scott Wood

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='CAHB2L+dbwNt8GxMYAvzZO-+WhOOuM_pyjq5XdSJ9Wm_=jHdoKw@mail.gmail.com' \
    --to=aijazbaig1@gmail.com \
    --cc=linuxppc-dev@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.