D.gnu - Dropping support for gcc 4.2.x to 4.4.x
- Iain Buclaw (8/8) Jan 03 2012 Morning,
- Jacob Carlborg (5/13) Jan 03 2012 That means no support for the Apple GCC. It's stuck at 4.2, I guess they...
- Iain Buclaw (11/33) Jan 04 2012 If I recall correctly, there are GCC binding to LLVM, are there not?
- Trass3r (4/6) Jan 04 2012 The post 4.2 one is DragonEgg.
- Iain Buclaw (13/45) Jan 04 2012 f
- Leandro Lucarella (9/14) Jan 05 2012 Does this have anything to do with merging GDC into GCC? How is that
- Iain Buclaw (8/16) Jan 05 2012 It will be ready when it's ready. My target is give or take when the
- Leandro Lucarella (9/24) Jan 06 2012 Cool, thanks!
- Vasileios Anagnostopoulos (2/21) Jan 05 2012 There is macports-gcc-4.5, macports-gcc-4.6
- Jacob Carlborg (4/27) Jan 06 2012 Yes, I know you can use the FSF GCC on Mac OS X.
- Manu (3/15) Jan 04 2012 This means some of those console toolchains won't work anymore, since
Morning, I will be dropping support for a few older gcc versions in the next week and a bit. I was thinking removing all code for everything up to gcc-4.5, meaning gdc will no longer build with gcc 4.2.x, 4.3.x and 4.4.x releases. If anyone has any objections, or requires continued support for these older versions of gcc, please let me know or shout up here, and I will make necessary arrangements. Regards Iain
Jan 03 2012
On 2012-01-04 01:33, Iain Buclaw wrote:Morning, I will be dropping support for a few older gcc versions in the next week and a bit. I was thinking removing all code for everything up to gcc-4.5, meaning gdc will no longer build with gcc 4.2.x, 4.3.x and 4.4.x releases. If anyone has any objections, or requires continued support for these older versions of gcc, please let me know or shout up here, and I will make necessary arrangements. Regards IainThat means no support for the Apple GCC. It's stuck at 4.2, I guess they putting their effort on Clang and LLVM. -- /Jacob Carlborg
Jan 03 2012
On 4 January 2012 07:14, Jacob Carlborg <doob me.com> wrote:On 2012-01-04 01:33, Iain Buclaw wrote:nsMorning, I will be dropping support for a few older gcc versions in the next week and a bit. I was thinking removing all code for everything up to gcc-4.5, meaning gdc will no longer build with gcc 4.2.x, 4.3.x and 4.4.x releases. =A0If anyone has any objections, or requires continued support for these older versio=If I recall correctly, there are GCC binding to LLVM, are there not? Apple has always been a bit of a difficult system for me as I don't have the OS to test on (actually, this is true for Windows too). I have made a new branch in the repository that is at the moment current and will maintain support for the older releases. If someone wishes to maintain it, I have no problem there. --=20 Iain Buclaw *(p < e ? p++ : p) =3D (c & 0x0f) + '0';of gcc, please let me know or shout up here, and I will make necessary arrangements. Regards IainThat means no support for the Apple GCC. It's stuck at 4.2, I guess they putting their effort on Clang and LLVM. -- /Jacob Carlborg
Jan 04 2012
On Wednesday, 4 January 2012 at 21:40:28 UTC, Iain Buclaw wrote:If I recall correctly, there are GCC binding to LLVM, are there not?The post 4.2 one is DragonEgg. It's a gcc plugin that replaces GCC's optimizers and code generators with those from llvm.
Jan 04 2012
On 4 January 2012 14:39, Iain Buclaw <ibuclaw ubuntu.com> wrote:On 4 January 2012 07:14, Jacob Carlborg <doob me.com> wrote:kOn 2012-01-04 01:33, Iain Buclaw wrote:Morning, I will be dropping support for a few older gcc versions in the next wee=fand a bit. I was thinking removing all code for everything up to gcc-4.5, meaning gdc will no longer build with gcc 4.2.x, 4.3.x and 4.4.x releases. =A0I=onsanyone has any objections, or requires continued support for these older versi=Also, bare in mind I will be moving GDC fully across to trunk over the next two months, this is just a first of many stop-gaps that will need to be done to update the code and cipher off any compatibilty hacks in favour of adding in and utilising new GCC tree codes that may help improve code generation. Regards --=20 Iain Buclaw *(p < e ? p++ : p) =3D (c & 0x0f) + '0';If I recall correctly, there are GCC binding to LLVM, are there not? Apple has always been a bit of a difficult system for me as I don't have the OS to test on (actually, this is true for Windows too). =A0 =A0I have made a new branch in the repository that is at the moment current and will maintain support for the older releases. =A0If someone wishes to maintain it, I have no problem there.of gcc, please let me know or shout up here, and I will make necessary arrangements. Regards IainThat means no support for the Apple GCC. It's stuck at 4.2, I guess they putting their effort on Clang and LLVM. -- /Jacob Carlborg
Jan 04 2012
Iain Buclaw, el 4 de enero a las 15:01 me escribiste:Also, bare in mind I will be moving GDC fully across to trunk over the next two months, this is just a first of many stop-gaps that will need to be done to update the code and cipher off any compatibilty hacks in favour of adding in and utilising new GCC tree codes that may help improve code generation.Does this have anything to do with merging GDC into GCC? How is that going BTW? -- Leandro Lucarella (AKA luca) http://llucax.com.ar/ ---------------------------------------------------------------------- GPG Key: 5F5A8D05 (F8CD F9A7 BF00 5431 4145 104C 949E BFB6 5F5A 8D05) ---------------------------------------------------------------------- El techo de mi cuarto lleno de cometas
Jan 05 2012
On 5 January 2012 09:47, Leandro Lucarella <luca llucax.com.ar> wrote:Iain Buclaw, el =A04 de enero a las 15:01 me escribiste:It will be ready when it's ready. My target is give or take when the 4.8 development window opens, I'll submit everything for inclusion. By then I will have dropped all backwards compatibility and #ifdef'd code. --=20 Iain Buclaw *(p < e ? p++ : p) =3D (c & 0x0f) + '0';Also, bare in mind I will be moving GDC fully across to trunk over the next two months, this is just a first of many stop-gaps that will need to be done to update the code and cipher off any compatibilty hacks in favour of adding in and utilising new GCC tree codes that may help improve code generation.Does this have anything to do with merging GDC into GCC? How is that going BTW?
Jan 05 2012
Iain Buclaw, el 5 de enero a las 23:21 me escribiste:On 5 January 2012 09:47, Leandro Lucarella <luca llucax.com.ar> wrote:Cool, thanks! -- Leandro Lucarella (AKA luca) http://llucax.com.ar/ ---------------------------------------------------------------------- GPG Key: 5F5A8D05 (F8CD F9A7 BF00 5431 4145 104C 949E BFB6 5F5A 8D05) ---------------------------------------------------------------------- Corrí muchas carreras, tratando de alcanzarte a vos. Pero corría sólo y siempre salí último.Iain Buclaw, el 4 de enero a las 15:01 me escribiste:It will be ready when it's ready. My target is give or take when the 4.8 development window opens, I'll submit everything for inclusion. By then I will have dropped all backwards compatibility and #ifdef'd code.Also, bare in mind I will be moving GDC fully across to trunk over the next two months, this is just a first of many stop-gaps that will need to be done to update the code and cipher off any compatibilty hacks in favour of adding in and utilising new GCC tree codes that may help improve code generation.Does this have anything to do with merging GDC into GCC? How is that going BTW?
Jan 06 2012
On 1/4/2012 9:14 AM, Jacob Carlborg wrote:On 2012-01-04 01:33, Iain Buclaw wrote:There is macports-gcc-4.5, macports-gcc-4.6Morning, I will be dropping support for a few older gcc versions in the next week and a bit. I was thinking removing all code for everything up to gcc-4.5, meaning gdc will no longer build with gcc 4.2.x, 4.3.x and 4.4.x releases. If anyone has any objections, or requires continued support for these older versions of gcc, please let me know or shout up here, and I will make necessary arrangements. Regards IainThat means no support for the Apple GCC. It's stuck at 4.2, I guess they putting their effort on Clang and LLVM.
Jan 05 2012
On 2012-01-05 10:29, Vasileios Anagnostopoulos wrote:On 1/4/2012 9:14 AM, Jacob Carlborg wrote:Yes, I know you can use the FSF GCC on Mac OS X. -- /Jacob CarlborgOn 2012-01-04 01:33, Iain Buclaw wrote:There is macports-gcc-4.5, macports-gcc-4.6Morning, I will be dropping support for a few older gcc versions in the next week and a bit. I was thinking removing all code for everything up to gcc-4.5, meaning gdc will no longer build with gcc 4.2.x, 4.3.x and 4.4.x releases. If anyone has any objections, or requires continued support for these older versions of gcc, please let me know or shout up here, and I will make necessary arrangements. Regards IainThat means no support for the Apple GCC. It's stuck at 4.2, I guess they putting their effort on Clang and LLVM.
Jan 06 2012
This means some of those console toolchains won't work anymore, since they're still on older versions... :( On 4 January 2012 02:33, Iain Buclaw <ibuclaw ubuntu.com> wrote:Morning, I will be dropping support for a few older gcc versions in the next week and a bit. I was thinking removing all code for everything up to gcc-4.5, meaning gdc will no longer build with gcc 4.2.x, 4.3.x and 4.4.x releases. If anyone has any objections, or requires continued support for these older versions of gcc, please let me know or shout up here, and I will make necessary arrangements. Regards Iain
Jan 04 2012