code review 6035054: lib9: fix warning under clang 3.1

lib9: fix warning under clang 3.1

Fixes issue 3534.

[dave_cheney.net, 2012-04-16 21:27:38]

Hello golang-dev@googlegroups.com,

I'd like you to review this change to
https://go.googlecode.com/hg/

[rsc, 2012-04-16 21:29:49]

LGTM

i see that clang is taking after gcc...

[dave_cheney.net, 2012-04-17 23:57:19]

*** Submitted as http://code.google.com/p/go/source/detail?r=73a10f76098b ***

lib9: fix warning under clang 3.1

Fixes issue 3534.

R=golang-dev, rsc
CC=golang-dev
http://codereview.appspot.com/6035054

[M-A, 2012-05-10 12:42:18]

On 2012/04/17 23:57:19, dfc wrote:
> *** Submitted as http://code.google.com/p/go/source/detail?r=73a10f76098b ***

Can this specific commit be merged into branch release-branch.go1 or is it out
of scope at that point? That's the only snag I hit when building this branch
when building with
> $CC --version
clang version 3.2 (trunk 155835)

Thanks,

M-A

[rsc, 2012-05-10 17:37:10]

On Thu, May 10, 2012 at 8:42 AM,  <maruel@chromium.org> wrote:
> Can this specific commit be merged into branch release-branch.go1 or is
> it out of scope at that point? That's the only snag I hit when building
> this branch when building with
>>
>> $CC --version
>
> clang version 3.2 (trunk 155835)

i created issue 3602 to remember to move it over for go 1.0.2.

thanks.
russ

[minux1, 2012-05-10 17:40:30]

On Fri, May 11, 2012 at 1:36 AM, Russ Cox <rsc@golang.org> wrote:

> On Thu, May 10, 2012 at 8:42 AM,  <maruel@chromium.org> wrote:
> > Can this specific commit be merged into branch release-branch.go1 or is
> > it out of scope at that point? That's the only snag I hit when building
> > this branch when building with
> >>
> >> $CC --version
> >
> > clang version 3.2 (trunk 155835)
>
> i created issue 3602 to remember to move it over for go 1.0.2.
>
actually it's issue 3608.