From: Paolo Bonzini <bonzini@gnu.org>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: "H.J. Lu" <hjl.tools@gmail.com>,
Richard Guenther <richard.guenther@gmail.com>,
DJ Delorie <dj@redhat.com>, Alexandre Oliva <aoliva@redhat.com>,
Ralf Wildenhues <Ralf.Wildenhues@gmx.de>,
neroden@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: PATCH [1/n] X32: Add initial -x32 support
Date: Thu, 07 Jul 2011 15:38:00 -0000 [thread overview]
Message-ID: <CAHFMJ7tKAODyJAM3qsHOn_zRfmqhe7EaUZhxPspZKGukhb-Nvw@mail.gmail.com> (raw)
In-Reply-To: <CAFULd4bnhGkAqho12fFu_EKYViiFWVYS8r161SA3T1emLcdhpg@mail.gmail.com>
On Thu, Jul 7, 2011 at 17:12, Uros Bizjak <ubizjak@gmail.com> wrote:
> On Thu, Jul 7, 2011 at 5:02 PM, H.J. Lu <hjl.tools@gmail.com> wrote:
>
>>> Did you even _think_ of looking at the sh configury, and do something
>>> vaguely similar for x86?
>>>
>>> You should not duplicate t-linux64 at all. Instead, in config.gcc set
>>> m64/m32 as the default value for with_multilib_list on i386 biarch and
>>> x86_64. Pass $with_multilib_list to t-linux64 using
>>> TM_MULTILIB_CONFIG. Then, do something like
>>>
>>> comma=,
>>> MULTILIB_OPTIONS = $(subst $(comma),/,@TM_MULTILIB_CONFIG@)
>>> MULTILIB_DIRNAMES = $(patsubst m%, %, $(subst /, ,$(MULTILIB_OPTIONS)))
>>> MULTILIB_OSDIRNAMES = 64=../lib64
>>> MULTILIB_OSDIRNAMES += 32=$(if $(wildcard $(shell echo
>>> $(SYSTEM_HEADER_DIR))/../../usr/lib32),../lib32,../lib)
>>> MULTILIB_OSDIRNAMES += x32=../libx32
>>>
>>> in config/t-linux64. (Each on one line, apologies for any wrapping)
>>>
>>> The option will be used as --with-multilib-list=m64,m32,mx32 (allowing
>>> the user to omit some of the variants, too).
>>>
>>
>> This is an excellent suggestion. Here is the updated patch. It
>> uses TM_MULTILIB_CONFIG and removes config/i386/t-linux-x32.
>>
>> Uros, is this OK for trunk to replace the patch you approved earlier?
>
> Er, the approval was fo x86 parts, I will leave approval for build
> parts to Paolo.
Yes, build parts are okay too.
Paolo
prev parent reply other threads:[~2011-07-07 15:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-05 19:55 PATCH [1/n]: " H.J. Lu
2011-06-06 15:47 ` Uros Bizjak
2011-06-07 15:47 ` Joseph S. Myers
2011-06-07 18:54 ` H.J. Lu
2011-06-07 19:19 ` Joseph S. Myers
2011-06-07 15:59 ` Joseph S. Myers
2011-06-07 19:11 ` H.J. Lu
2011-06-07 19:20 ` Joseph S. Myers
2011-06-07 22:02 ` H.J. Lu
2011-06-14 17:52 ` H.J. Lu
2011-07-05 14:42 ` PATCH [1/n] X32: " H.J. Lu
2011-07-05 15:21 ` Uros Bizjak
2011-07-05 17:59 ` H.J. Lu
2011-07-05 18:18 ` Uros Bizjak
2011-07-05 19:09 ` H.J. Lu
2011-07-05 19:09 ` Joseph S. Myers
2011-07-05 20:07 ` Uros Bizjak
2011-07-06 14:50 ` H.J. Lu
2011-07-06 15:03 ` Richard Guenther
2011-07-06 16:40 ` H.J. Lu
2011-07-07 13:03 ` H.J. Lu
2011-07-07 13:08 ` Uros Bizjak
2011-07-07 13:27 ` Paolo Bonzini
2011-07-07 15:10 ` H.J. Lu
2011-07-07 15:14 ` Uros Bizjak
2011-07-07 15:38 ` Paolo Bonzini [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=CAHFMJ7tKAODyJAM3qsHOn_zRfmqhe7EaUZhxPspZKGukhb-Nvw@mail.gmail.com \
--to=bonzini@gnu.org \
--cc=Ralf.Wildenhues@gmx.de \
--cc=aoliva@redhat.com \
--cc=dj@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=neroden@gcc.gnu.org \
--cc=richard.guenther@gmail.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).