All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Aníbal Limón" <anibal.limon@linux.intel.com>
To: Simon Horman <horms@verge.net.au>
Cc: kexec@lists.infradead.org
Subject: Re: [PATCH] x86_64: Add support to build kexec-tools with x32 ABI
Date: Wed, 08 Apr 2015 12:53:46 -0500	[thread overview]
Message-ID: <55256B2A.4070001@linux.intel.com> (raw)
In-Reply-To: <20150407012350.GA27486@verge.net.au>

Hi Simon,

I did more testing and found that the patch causes a fail when try to 
compile with zlib and other arch not
x86_64, it's related to AC_EGREP_CPP needs previous AC_PROG_CC.

I sent a patch for that,

http://lists.infradead.org/pipermail/kexec/2015-April/013554.html

Sorry for the problems that i may have caused.

Kind regards,
     alimon

On 06/04/15 20:23, Simon Horman wrote:
> On Mon, Apr 06, 2015 at 10:55:47AM -0500, Aníbal Limón wrote:
>> On 05/04/15 20:04, Simon Horman wrote:
>>> On Fri, Apr 03, 2015 at 10:05:06AM -0600, Aníbal Limón wrote:
>>>> Any comment or feedback?
>>> I feel like I am missing something obvious, but
>>> could you explain the use case a little more clearly?
>> I'm working in the Yocto Project enabling x32 ABI support, the x32 ABI
>> enables
>> programs to work with 32-bit address space and support of benefits of 64-bit
>> mode
>> like register calling convention, this improves performance in some
>> applications,
>> details [1][2].
>>
>> I don't know if this answer your question?
> Thanks, that answers my question very well.
> I have applied your patch.



_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2015-04-08 17:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-26 16:19 [PATCH] x86_64: Add support to build kexec-tools with x32 ABI Aníbal Limón
2015-04-03 16:05 ` Aníbal Limón
2015-04-06  1:04   ` Simon Horman
2015-04-06 15:55     ` Aníbal Limón
2015-04-07  1:23       ` Simon Horman
2015-04-08 17:53         ` Aníbal Limón [this message]
2015-04-09  2:10           ` Simon Horman

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=55256B2A.4070001@linux.intel.com \
    --to=anibal.limon@linux.intel.com \
    --cc=horms@verge.net.au \
    --cc=kexec@lists.infradead.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.