On Thu, Jul 7, 2011 at 17:12, Uros Bizjak wrote:
> On Thu, Jul 7, 2011 at 5:02 PM, H.J. Lu 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
On Thu, Jul 7, 2011 at 5:02 PM, H.J. Lu 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 an
On Thu, Jul 7, 2011 at 6:21 AM, Paolo Bonzini 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 an
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_MULTI
On Thu, Jul 7, 2011 at 2:59 PM, H.J. Lu wrote:
Hi Paolo, DJ, Nathanael, Alexandre, Ralf,
Is the change
.
* configure.ac: Support --enable-x32.
* configure: Regenerated.
diff --git a/gcc/configure.ac b/gcc/configure.ac
index 5f3641b..bddab
On Wed, Jul 6, 2011 at 9:22 AM, H.J. Lu wrote:
> On Wed, Jul 6, 2011 at 8:02 AM, Richard Guenther
> wrote:
>> On Wed, Jul 6, 2011 at 4:48 PM, H.J. Lu wrote:
>>> Hi Paolo, DJ, Nathanael, Alexandre, Ralf,
>>>
>>> Is the change
>>> .
>>> * configure.ac: Support --enable-x32.
>>> * con
On Wed, Jul 6, 2011 at 8:02 AM, Richard Guenther
wrote:
> On Wed, Jul 6, 2011 at 4:48 PM, H.J. Lu wrote:
>> Hi Paolo, DJ, Nathanael, Alexandre, Ralf,
>>
>> Is the change
>> .
>> * configure.ac: Support --enable-x32.
>> * configure: Regenerated.
>>
>> diff --git a/gcc/configure.ac b/
On Wed, Jul 6, 2011 at 4:48 PM, H.J. Lu wrote:
> Hi Paolo, DJ, Nathanael, Alexandre, Ralf,
>
> Is the change
> .
> * configure.ac: Support --enable-x32.
> * configure: Regenerated.
>
> diff --git a/gcc/configure.ac b/gcc/configure.ac
> index 5f3641b..bddabeb 100644
> --- a/gcc/config
Hi Paolo, DJ, Nathanael, Alexandre, Ralf,
Is the change
.
* configure.ac: Support --enable-x32.
* configure: Regenerated.
diff --git a/gcc/configure.ac b/gcc/configure.ac
index 5f3641b..bddabeb 100644
--- a/gcc/configure.ac
+++ b/gcc/configure.ac
@@ -611,6 +611,11 @@ AC_ARG_ENABLE
On Tue, Jul 5, 2011 at 8:49 PM, H.J. Lu wrote:
>> #undef LINK_SPEC
>> #define LINK_SPEC "%{" SPEC_64 ":-m " GNU_USER_LINK_EMULATION64 "} \
>> %{" SPEC_32 ":-m " GNU_USER_LINK_EMULATION32 "} \
>> + %{" SPEC_X32 ":-m " GNU_USER_LINK_EMULATIONX32 "} \
>> %{sh
On Tue, 5 Jul 2011, H.J. Lu wrote:
> > I really think that "!(m64|mx32)" is more descriptive and clear...
>
> I don't know if gcc spec supports it. I just followed mips backend.
Indeed, I don't think any such grouping construct exists in specs.
The .opt changes look fine to me.
--
Joseph S.
On Tue, Jul 5, 2011 at 11:14 AM, Uros Bizjak wrote:
> On Tue, Jul 5, 2011 at 7:54 PM, H.J. Lu wrote:
>
I'd like to start submitting a series of patches to enable x32:
https://sites.google.com/site/x32abi/
The GCC x32 branch is very stable. There are no unexpected failures
On Tue, Jul 5, 2011 at 7:54 PM, H.J. Lu wrote:
>>> I'd like to start submitting a series of patches to enable x32:
>>>
>>> https://sites.google.com/site/x32abi/
>>>
>>> The GCC x32 branch is very stable. There are no unexpected failures in
>>> C, C++, Fortran and Objective C testsuites. SPEC CPU
On Tue, Jul 5, 2011 at 8:16 AM, Uros Bizjak wrote:
> On Tue, Jul 5, 2011 at 4:39 PM, H.J. Lu wrote:
>
>> I'd like to start submitting a series of patches to enable x32:
>>
>> https://sites.google.com/site/x32abi/
>>
>> The GCC x32 branch is very stable. There are no unexpected failures in
>> C, C
On Tue, Jul 5, 2011 at 4:39 PM, H.J. Lu wrote:
> I'd like to start submitting a series of patches to enable x32:
>
> https://sites.google.com/site/x32abi/
>
> The GCC x32 branch is very stable. There are no unexpected failures in
> C, C++, Fortran and Objective C testsuites. SPEC CPU 2K/2006 com
Hi,
I'd like to start submitting a series of patches to enable x32:
https://sites.google.com/site/x32abi/
The GCC x32 branch is very stable. There are no unexpected failures in
C, C++, Fortran and Objective C testsuites. SPEC CPU 2K/2006 compile
and run correctly at -O2 and -O3.
More than 90%
16 matches
Mail list logo