On Sat, Nov 15, 2014 at 07:46:40AM -0800, Ian Taylor wrote:
> On Thu, Nov 13, 2014 at 2:58 AM, Dominik Vogt wrote:
> > What do you think about the attached patches? They work for me, but I'm
> > not sure whether the patch to go-test.exp is good because I know
> > nothing about tcl.
>
> Looks pla
On Thu, Nov 13, 2014 at 2:58 AM, Dominik Vogt wrote:
>
> What do you think about the attached patches? They work for me, but I'm
> not sure whether the patch to go-test.exp is good because I know
> nothing about tcl.
Looks plausible to me.
Ian
On Fri, Nov 07, 2014 at 08:24:15AM -0800, Ian Taylor wrote:
> On Fri, Nov 7, 2014 at 12:51 AM, Dominik Vogt wrote:
> > On Thu, Nov 06, 2014 at 09:06:18AM -0800, Ian Taylor wrote:
> >> On Thu, Nov 6, 2014 at 4:04 AM, Dominik Vogt
> >> wrote:
> >> > On Tue, Nov 04, 2014 at 08:16:51PM -0800, Ian Ta
On Mon, Nov 10, 2014 at 6:00 AM, Dominik Vogt wrote:
>> I'd still like to avoid the rampant duplication if possible. One
>> approach would be to put most of the test in something like
>> nilptr_tests.go marked with "// skip". Then we can have top-level
>> nilptrXX.go tests with +build lines that
> I'd still like to avoid the rampant duplication if possible. One
> approach would be to put most of the test in something like
> nilptr_tests.go marked with "// skip". Then we can have top-level
> nilptrXX.go tests with +build lines that use "// run nilptr_tests.go".
I fail to see how that cou
Ian Taylor writes:
> I don't know what's up with the complex number change. In general the
> Go compiler and libraries go to some effort to produce the same
> answers on all platforms. We need to understand why we get different
> answers on s390 (you may understand the differences, but I don't)
On Fri, Nov 7, 2014 at 12:51 AM, Dominik Vogt wrote:
> On Thu, Nov 06, 2014 at 09:06:18AM -0800, Ian Taylor wrote:
>> On Thu, Nov 6, 2014 at 4:04 AM, Dominik Vogt wrote:
>> > On Tue, Nov 04, 2014 at 08:16:51PM -0800, Ian Taylor wrote:
>> >> The way to do it is not by
>> >> copying the test. If t
On Thu, Nov 06, 2014 at 09:06:18AM -0800, Ian Taylor wrote:
> On Thu, Nov 6, 2014 at 4:04 AM, Dominik Vogt wrote:
> > On Tue, Nov 04, 2014 at 08:16:51PM -0800, Ian Taylor wrote:
> >> The way to do it is not by
> >> copying the test. If the test needs to be customized, add additional
> >> files th
On Thu, Nov 6, 2014 at 4:04 AM, Dominik Vogt wrote:
> On Tue, Nov 04, 2014 at 08:16:51PM -0800, Ian Taylor wrote:
>> The way to do it is not by
>> copying the test. If the test needs to be customized, add additional
>> files that use // +build lines to pick which files is built. Move
>> them int
On Tue, Nov 04, 2014 at 08:16:51PM -0800, Ian Taylor wrote:
> The way to do it is not by
> copying the test. If the test needs to be customized, add additional
> files that use // +build lines to pick which files is built. Move
> them into a directory, like method4.go or other tests that use
> "r
On Wed, Nov 5, 2014 at 2:05 AM, Dominik Vogt wrote:
> On Tue, Nov 04, 2014 at 08:16:51PM -0800, Ian Taylor wrote:
>> I committed the change to go-test.exp. Thanks.
>>
>> The other changes are not OK. As described in
>> gcc/testsuite/go.test/test/README.gcc, the files in
>> gcc/testsuite/go.test/
On Tue, Nov 04, 2014 at 08:16:51PM -0800, Ian Taylor wrote:
> I committed the change to go-test.exp. Thanks.
>
> The other changes are not OK. As described in
> gcc/testsuite/go.test/test/README.gcc, the files in
> gcc/testsuite/go.test/test are an exact copy of the master Go
> testsuite. Any c
I committed the change to go-test.exp. Thanks.
The other changes are not OK. As described in
gcc/testsuite/go.test/test/README.gcc, the files in
gcc/testsuite/go.test/test are an exact copy of the master Go
testsuite. Any changes must be made to the master Go testsuite first.
I don't know what
13 matches
Mail list logo
