All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wanlong Gao <gaowanlong@cn.fujitsu.com>
To: Chris Dearman <chris@mips.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] Avoid compiler optimisation of malloc calls
Date: Thu, 18 Oct 2012 09:36:03 +0800	[thread overview]
Message-ID: <507F5D03.5010109@cn.fujitsu.com> (raw)
In-Reply-To: <20121017173535.11574.18883.stgit@localhost6.localdomain6>

On 10/18/2012 01:35 AM, Chris Dearman wrote:
> clang understands the malloc library call and can optimise calls to
> it. In particular it will avoid calling malloc completely if it
> detects that the result is not used.
> 
> Signed-off-by: Chris Dearman <chris@mips.com>

Pushed with Cyril's Ack, thank you.

Wanlong Gao

> ---
>  .../conformance/interfaces/pthread_cond_init/4-1.c |   19 ++++++++++++-------
>  1 file changed, 12 insertions(+), 7 deletions(-)
> 
> 
> 
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_sfd2d_oct
> 
> 
> 
> _______________________________________________
> Ltp-list mailing list
> Ltp-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ltp-list
> 


------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

      reply	other threads:[~2012-10-18  1:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-16 14:17 [LTP] [PATCH] Avoid compiler optimisation of malloc calls Chris Dearman
2012-10-17 16:04 ` chrubis
2012-10-17 17:35 ` Chris Dearman
2012-10-18  1:36   ` Wanlong Gao [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=507F5D03.5010109@cn.fujitsu.com \
    --to=gaowanlong@cn.fujitsu.com \
    --cc=chris@mips.com \
    --cc=ltp-list@lists.sourceforge.net \
    /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.