public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: vaibhav <v.bhav.shinde@gmail.com>
To: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] Openposix: pthread create, testcase  1-6
Date: Sat, 9 Jun 2012 12:38:39 +0000 (UTC)	[thread overview]
Message-ID: <loom.20120609T143221-953@post.gmane.org> (raw)
In-Reply-To: 200712032347.17105.vapier@gentoo.org



Mike Frysinger <vapier@...> writes:

> 
> On Monday 03 December 2007, Patrick Kirsch wrote:
> > I have a question on testcase pthread_create/1-1.c :
> > there is shared variable "int *ctrl = (int *) arg;" in function
> > "hp_func" which should be protected through pthread_mutex or similar,
> > right? As I understand this shared variable should always be protected?
> > So is there a reason why there are no pthread synchronisation calls?
> >
> > As you can see in the suggested temporary patch below, is it possible to
> > add volatile-statement to the shared variables?
> >
> > I'm asking, because sometimes this testcase fails on s390x.
> 
> perhaps look at the generated assembly code and see if gcc is incorrectly 
> optimizing away memory loads ?  adding volatile sounds like you're ignoring a 
> deeper problem ...
> -mike

Hi Mike

This test case is released with volatile variable usage in LTP january release. 
I tested it for MIPS target, it FAILS giving error : 

volatile int *ctrl = (int *) arg; 

Can you please point out whats could be the exact issue? 

Looking forward to your reply. 

Thanks,
Vaibhav 
> 
> 
> -------------------------------------------------------------------------
> SF.Net email is sponsored by: The Future of Linux Business White Paper
> from Novell.  From the desktop to the data center, Linux is going
> mainstream.  Let it simplify your IT future.
> http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
> 
> _______________________________________________
> Ltp-list mailing list
> Ltp-list@...
> https://lists.sourceforge.net/lists/listinfo/ltp-list
> 



------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

       reply	other threads:[~2012-06-09 16:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4753F3FA.3010601@suse.de>
     [not found] ` <200712032347.17105.vapier@gentoo.org>
2012-06-09 12:38   ` vaibhav [this message]
2012-06-13  6:59 [LTP] Openposix: pthread create, testcase 1-6 naresh kamboju

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=loom.20120609T143221-953@post.gmane.org \
    --to=v.bhav.shinde@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox