public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Richard Palethorpe <rpalethorpe@suse.de>
To: ltp@lists.linux.it
Subject: [LTP] [RFC] [PATCH v2] lib32: Add support for linking 32bit programs on 64bit
Date: Tue, 16 May 2017 10:38:56 +0200	[thread overview]
Message-ID: <87lgpx8acf.fsf@our.domain.is.not.set> (raw)
In-Reply-To: <20170406124641.30179-1-chrubis@suse.cz>

Hi,

Cyril Hrubis writes:

> This is proof of concept for building 32bit testcases on 64bit platform.
>
> What we do is:
>
> * Configure test if compiler supports -m32
>
> * Configure test if compiler supports atomic operations with -m32
>   (we have to use fallbacks in tst_atomic.h otherwise)
>
> * The directory lib32 contains symlinks of minimal set of sources
>   needed to link newlib testcase + Makefile.
>
> * The testcases.mk builds 32bit library as well if
>   32bit compiler was installed (-m32 configure test was succesful)
>
> * And finally the env_post.mk switches between adding -L path to lib or
>   lib32 depeding on if -m32 was passed in global CFLAGS and/or in the
>   target specific CFLAGS

I'm not sure if this has already been taken into account, but on aarch64
gcc does not recognise the -m32 switch and compilation fails if the test
case has added -m32 to its CFLAGS.

-- 
Thank you,
Richard.

  parent reply	other threads:[~2017-05-16  8:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-06 12:46 [LTP] [RFC] [PATCH v2] lib32: Add support for linking 32bit programs on 64bit Cyril Hrubis
2017-04-07  8:58 ` Richard Palethorpe
2017-04-07  9:19   ` Cyril Hrubis
2017-04-07 11:32     ` Richard Palethorpe
2017-04-07 11:44       ` Cyril Hrubis
2017-05-16  8:38 ` Richard Palethorpe [this message]
2017-05-16 16:00 ` Jiri Jaburek

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=87lgpx8acf.fsf@our.domain.is.not.set \
    --to=rpalethorpe@suse.de \
    --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