This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Cygwin x86_64 support for GCC 4.8.x
- From: Vasili Galka <vvv444 at gmail dot com>
- To: Kai Tietz <ktietz70 at googlemail dot com>
- Cc: GCC Patches <gcc-patches at gcc dot gnu dot org>
- Date: Sat, 7 Sep 2013 21:47:05 +0300
- Subject: Re: Cygwin x86_64 support for GCC 4.8.x
- Authentication-results: sourceware.org; auth=none
- References: <CA+gZxsMjWn_Sg3FMF_XTPK-mjnHWBzvDb4XqXAyd0mt3+gtSxg at mail dot gmail dot com> <CAEwic4Z57X4QqS6f5qtN9Gbr_jzOo=jn0VfX6OruRvr8666JGA at mail dot gmail dot com>
Hi Kai,
I see. My apologies, I'm not familiar with the GCC merging policy.
In any case, where does GCC document the list of supported
target/host/build configurations?
I was trying to build GCC 4.8.1 with following configuration: HOST &
BUILD: Cygwin 64bit, TARGET=arm-none-eabi
I ended up with successful build/install that generated runtime errors
which I had to investigate (while same on Cygwin 32 was fine).
So it shall be either documented that such configuration is not
supported or (better) it shall generate a warning/error at configure stage.
Best,
Vasili
On Sat, Sep 7, 2013 at 9:37 PM, Kai Tietz <ktietz70@googlemail.com> wrote:
> 2013/9/7 Vasili Galka <vvv444@gmail.com>:
>> Hi,
>>
>> Cygwin x86_64 support was implemented on trunk r197171. Given it is a
>> minor configuration files change I recommend merging it to GCC 4.8
>> branch.
>>
>> Best regards,
>> Vasili
>
> No, this won't be back-merged. It isn't a "minor configuration file change".
> The gcc 4.9 series will be the first official gcc supporting cygwin
> 64-bit target.
>
> Regards,
> Kai