public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] Pre-release LTP build
Date: Tue, 12 Apr 2016 04:29:33 -0400 (EDT)	[thread overview]
Message-ID: <1944071328.394698.1460449773165.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20160411172305.GC3466@rei.lan>



----- Original Message -----
> From: "Cyril Hrubis" <chrubis@suse.cz>
> To: ltp@lists.linux.it
> Sent: Monday, 11 April, 2016 7:23:05 PM
> Subject: [LTP] Pre-release LTP build
> 
> Hi!
> I've tried to build LTP source for several distributions and as I
> expected the support for compiler atomic operations is missing in old
> compilers. Particulary gcc-4.1 on x86 (32bit RHEL5) and gcc-3.4 (SLES9)
> and older which were released in 2007 and 2006.
> 
> The questions is: do we care enough to provide fallback inline assembler?
> 
> I would be inclined to say that we don't. So does anybody out there
> still uses LTP with a compiler old enough that it does not support
> atomic builtins?

I do. At least RHEL5.6 is going to be around for another year.

I have repeatedly built your patch-series on RHEL5.6 x86_64, which works
fine. But as you pointed out 32bit version fails, other arches possibly too.

My first thought was some kind of lock, so we don't have to care
about each architecture separately.

  reply	other threads:[~2016-04-12  8:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-11 17:23 [LTP] Pre-release LTP build Cyril Hrubis
2016-04-12  8:29 ` Jan Stancek [this message]
2016-04-12  8:40   ` Cyril Hrubis
2016-04-12 11:57     ` Jan Stancek
2016-04-12 12:23       ` Cyril Hrubis
2016-04-12 13:39         ` Jan Stancek
2016-04-12 14:24           ` Cyril Hrubis
2016-04-13 13:07             ` Jan Stancek
2016-04-13 13:30               ` Cyril Hrubis

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=1944071328.394698.1460449773165.JavaMail.zimbra@redhat.com \
    --to=jstancek@redhat.com \
    --cc=ltp@lists.linux.it \
    /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