public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Cc: Jakub Jelinek <jakub@redhat.com>, Uros Bizjak <ubizjak@gmail.com>
Subject: PING^2: [PATCH] PR target/70454: Build x86 libgomp with -march=i486 or better
Date: Mon, 09 May 2016 12:53:00 -0000	[thread overview]
Message-ID: <CAMe9rOrqp9rijW_TmkrhtDdsku4ZaETfxdP+tp+hmaJHi1cYqQ@mail.gmail.com> (raw)

On Mon, May 2, 2016 at 6:46 AM, H.J. Lu <hjl.tools@gmail.com> wrote:
> On Mon, Apr 25, 2016 at 1:36 PM, H.J. Lu <hongjiu.lu@intel.com> wrote:
>> If x86 libgomp isn't compiled with -march=i486 or better, append
>> -march=i486 XCFLAGS for x86 libgomp build.
>>
>> Tested on i686 with and without --with-arch=i386.  Tested on
>> x86-64 with and without --with-arch_32=i386.  OK for trunk?
>>
>>
>> H.J.
>> ---
>>         PR target/70454
>>         * configure.tgt (XCFLAGS): Append -march=i486 to compile x86
>>         libgomp if needed.
>> ---
>>  libgomp/configure.tgt | 36 ++++++++++++++++--------------------
>>  1 file changed, 16 insertions(+), 20 deletions(-)
>>
>> diff --git a/libgomp/configure.tgt b/libgomp/configure.tgt
>> index 77e73f0..c876e80 100644
>> --- a/libgomp/configure.tgt
>> +++ b/libgomp/configure.tgt
>> @@ -67,28 +67,24 @@ if test x$enable_linux_futex = xyes; then
>>         ;;
>>
>>      # Note that bare i386 is not included here.  We need cmpxchg.
>> -    i[456]86-*-linux*)
>> +    i[456]86-*-linux* | x86_64-*-linux*)
>>         config_path="linux/x86 linux posix"
>> -       case " ${CC} ${CFLAGS} " in
>> -         *" -m64 "*|*" -mx32 "*)
>> -           ;;
>> -         *)
>> -           if test -z "$with_arch"; then
>> -             XCFLAGS="${XCFLAGS} -march=i486 -mtune=${target_cpu}"
>> +       # Need i486 or better.
>> +       cat > conftestx.c <<EOF
>> +#if defined __x86_64__ || defined __i486__ || defined __pentium__ \
>> +      || defined __pentiumpro__ || defined __pentium4__ \
>> +      || defined __geode__ || defined __SSE__
>> +# error Need i486 or better
>> +#endif
>> +EOF
>> +       if ${CC} ${CFLAGS} -c -o conftestx.o conftestx.c > /dev/null 2>&1; then
>> +           if test "${target_cpu}" = x86_64; then
>> +               XCFLAGS="${XCFLAGS} -march=i486 -mtune=generic"
>> +           else
>> +               XCFLAGS="${XCFLAGS} -march=i486 -mtune=${target_cpu}"
>>             fi
>> -       esac
>> -       ;;
>> -
>> -    # Similar jiggery-pokery for x86_64 multilibs, except here we
>> -    # can't rely on the --with-arch configure option, since that
>> -    # applies to the 64-bit side.
>> -    x86_64-*-linux*)
>> -       config_path="linux/x86 linux posix"
>> -       case " ${CC} ${CFLAGS} " in
>> -         *" -m32 "*)
>> -           XCFLAGS="${XCFLAGS} -march=i486 -mtune=generic"
>> -           ;;
>> -       esac
>> +       fi
>> +       rm -f conftestx.c conftestx.o
>>         ;;
>>
>>      # Note that sparcv7 and sparcv8 is not included here.  We need cas.
>> --
>> 2.5.5
>>
>
> PING.
>

PING.

-- 
H.J.

                 reply	other threads:[~2016-05-09 12:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAMe9rOrqp9rijW_TmkrhtDdsku4ZaETfxdP+tp+hmaJHi1cYqQ@mail.gmail.com \
    --to=hjl.tools@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=ubizjak@gmail.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).