On 01/13/2015 07:35 AM, H.J. Lu wrote:
> Can I apply it to GCC trunk?
Please.
r~
On Mon, Jan 12, 2015 at 5:13 PM, Richard Henderson wrote:
> On 01/12/2015 04:57 PM, H.J. Lu wrote:
>> The problem is my x86_64-*-linux-gnux32 patch
>>
>> https://gcc.gnu.org/ml/gcc-patches/2012-08/msg01083.html
>>
>> was never accepted upstream. Can I apply it to config.guess
>> in GCC?
>
> Ah.
On 01/12/2015 04:57 PM, H.J. Lu wrote:
> The problem is my x86_64-*-linux-gnux32 patch
>
> https://gcc.gnu.org/ml/gcc-patches/2012-08/msg01083.html
>
> was never accepted upstream. Can I apply it to config.guess
> in GCC?
Ah. Hmm. Perhaps the configure.host patch would be better after all.
On Mon, Jan 12, 2015 at 3:46 PM, H.J. Lu wrote:
> On Mon, Jan 12, 2015 at 2:42 PM, H.J. Lu wrote:
>> This libffi commit:
>>
>> 13e2d7b92557a9511a0414df82bf2df3edc55cba is the first bad commit
>> commit 13e2d7b92557a9511a0414df82bf2df3edc55cba
>> Author: Anthony Green
>> Date: Thu Jan 10 10:52:
On Mon, Jan 12, 2015 at 4:29 PM, Richard Henderson wrote:
> On 01/12/2015 03:46 PM, H.J. Lu wrote:
>> On Mon, Jan 12, 2015 at 2:42 PM, H.J. Lu wrote:
>>> This libffi commit:
>>>
>>> 13e2d7b92557a9511a0414df82bf2df3edc55cba is the first bad commit
>>> commit 13e2d7b92557a9511a0414df82bf2df3edc55cb
On 01/12/2015 03:46 PM, H.J. Lu wrote:
> On Mon, Jan 12, 2015 at 2:42 PM, H.J. Lu wrote:
>> This libffi commit:
>>
>> 13e2d7b92557a9511a0414df82bf2df3edc55cba is the first bad commit
>> commit 13e2d7b92557a9511a0414df82bf2df3edc55cba
>> Author: Anthony Green
>> Date: Thu Jan 10 10:52:02 2013 -0
On Mon, Jan 12, 2015 at 2:42 PM, H.J. Lu wrote:
> This libffi commit:
>
> 13e2d7b92557a9511a0414df82bf2df3edc55cba is the first bad commit
> commit 13e2d7b92557a9511a0414df82bf2df3edc55cba
> Author: Anthony Green
> Date: Thu Jan 10 10:52:02 2013 -0500
>
> Handle both 32 and 64-bit x86 build
This libffi commit:
13e2d7b92557a9511a0414df82bf2df3edc55cba is the first bad commit
commit 13e2d7b92557a9511a0414df82bf2df3edc55cba
Author: Anthony Green
Date: Thu Jan 10 10:52:02 2013 -0500
Handle both 32 and 64-bit x86 builds regardless of target triple
breaks x32.
--
H.J.