This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [buildrobot] Re: [PATCH] Split -fisolate-erroneous-paths into two options


On Thu, Dec 5, 2013 at 9:03 AM, Jeff Law <law@redhat.com> wrote:
>
> Q. Now that we're in stage3, presumably GO imports onto the trunk are
> stopping?  If so would it make sense to enable GO by default?

The Go library will no longer be updated except for bug fixes.  If
there is a Go 1.2.1 release, and if it is released before GCC 4.9.0,
then I plan to bring those library changes in before the GCC release.
However, those changes, if any, would be small.  Go has a fairly
strict policy on x.y.z patches: only those that address critical bugs
with no workaround.

However, I do still plan to update the files in gcc/testsuite/go.test
to the 1.2 set of tests, and that may require some follow-on patches
to the Go frontend.  This is to pursue the goal of having solid Go 1.2
support in the GCC 4.9.0 release.  So while enabling Go by default is
an interesting idea I think it is premature.

Ian


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]