On Fri, Feb 8, 2013 at 3:07 AM, Ian Lance Taylor i...@google.com wrote:
On Thu, Feb 7, 2013 at 2:43 PM, Uros Bizjak ubiz...@gmail.com wrote:
I did hit one new error that seems related:
--- FAIL: TestChtimes (0.00 seconds)
os_test.go:681: AccessTime didn't go backwards;
On Fri, Feb 8, 2013 at 6:42 AM, Uros Bizjak ubiz...@gmail.com wrote:
On Fri, Feb 8, 2013 at 3:07 AM, Ian Lance Taylor i...@google.com wrote:
On Thu, Feb 7, 2013 at 2:43 PM, Uros Bizjak ubiz...@gmail.com wrote:
I did hit one new error that seems related:
--- FAIL: TestChtimes (0.00 seconds)
On Fri, Feb 8, 2013 at 4:02 PM, Ian Lance Taylor i...@google.com wrote:
I did hit one new error that seems related:
--- FAIL: TestChtimes (0.00 seconds)
os_test.go:681: AccessTime didn't go backwards;
was={63495872497 0 47130825733376}, after={63495872497 0
47130825733376}
On Fri, Feb 8, 2013 at 7:23 AM, Uros Bizjak ubiz...@gmail.com wrote:
On Fri, Feb 8, 2013 at 4:02 PM, Ian Lance Taylor i...@google.com wrote:
I did hit one new error that seems related:
--- FAIL: TestChtimes (0.00 seconds)
os_test.go:681: AccessTime didn't go backwards;
On Fri, Feb 8, 2013 at 5:21 PM, Ian Lance Taylor i...@google.com wrote:
On Fri, Feb 8, 2013 at 7:23 AM, Uros Bizjak ubiz...@gmail.com wrote:
On Fri, Feb 8, 2013 at 4:02 PM, Ian Lance Taylor i...@google.com wrote:
I did hit one new error that seems related:
--- FAIL: TestChtimes (0.00
On Fri, Feb 8, 2013 at 8:48 AM, Uros Bizjak ubiz...@gmail.com wrote:
utimensat returns zero on CentOS. Following is gdb session:
Thanks--can you do the same session but with step instead of next?
Ian
On Fri, Feb 8, 2013 at 5:53 PM, Ian Lance Taylor i...@google.com wrote:
On Fri, Feb 8, 2013 at 8:48 AM, Uros Bizjak ubiz...@gmail.com wrote:
utimensat returns zero on CentOS. Following is gdb session:
Thanks--can you do the same session but with step instead of next?
I think I got the
On Fri, Feb 8, 2013 at 6:10 PM, Uros Bizjak ubiz...@gmail.com wrote:
On Fri, Feb 8, 2013 at 5:53 PM, Ian Lance Taylor i...@google.com wrote:
On Fri, Feb 8, 2013 at 8:48 AM, Uros Bizjak ubiz...@gmail.com wrote:
utimensat returns zero on CentOS. Following is gdb session:
Thanks--can you do the
On Fri, Feb 8, 2013 at 9:42 AM, Uros Bizjak ubiz...@gmail.com wrote:
Please note, that looking at generated libcalls.go, there are many
other possible signed/unsigned issues of the same type. Since this all
happens on x86_64 (where go int is apparently 64bit), it looks that it
is very
On Tue, Feb 5, 2013 at 9:00 PM, Ian Lance Taylor i...@google.com wrote:
On Thu, Jan 3, 2013 at 1:26 AM, Uros Bizjak ubiz...@gmail.com wrote:
Hello!
I've committed a patch to upgrade libgo to the current version of the
master Go library. As usual, this mail message only includes the
changes
On Thu, Feb 7, 2013 at 2:26 AM, Uros Bizjak ubiz...@gmail.com wrote:
Thanks, I have tested it on CentOS 5.9. However, for some reason, I
got unrelated linker errors that prevents further testing:
=== libgo tests ===
./a.out: error while loading shared libraries:
On Thu, Feb 7, 2013 at 5:27 PM, Ian Lance Taylor i...@google.com wrote:
On Thu, Feb 7, 2013 at 2:26 AM, Uros Bizjak ubiz...@gmail.com wrote:
Thanks, I have tested it on CentOS 5.9. However, for some reason, I
got unrelated linker errors that prevents further testing:
===
On Thu, Jan 3, 2013 at 1:26 AM, Uros Bizjak ubiz...@gmail.com wrote:
Hello!
I've committed a patch to upgrade libgo to the current version of the
master Go library. As usual, this mail message only includes the
changes to files that are specific to gccgo. Bootstrapped and ran Go
testsuite
Hello!
I've committed a patch to upgrade libgo to the current version of the
master Go library. As usual, this mail message only includes the
changes to files that are specific to gccgo. Bootstrapped and ran Go
testsuite on x86_64-unknown-linux-gnu. Committed to mainline.
This caused
I've committed a patch to upgrade libgo to the current version of the
master Go library. As usual, this mail message only includes the
changes to files that are specific to gccgo. Bootstrapped and ran Go
testsuite on x86_64-unknown-linux-gnu. Committed to mainline.
Ian
diff -r 1faae2fad711
I've committed a patch to libgo to update to the current version of the
master Go library. The patch is too large to include here, and is in
any case simply a copy of changes available in the master Go library
repository. See SVN or http://codereview.appspot.com/4281068/ for the
changes as
16 matches
Mail list logo
