Skip to content
Projects
Groups
Snippets
Help
Loading...
Sign in
Toggle navigation
G
golang
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Commits
Issue Boards
Open sidebar
go
golang
Commits
b8035ab5
Commit
b8035ab5
authored
Apr 08, 2009
by
Russ Cox
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
bug142
R=ken OCL=27202 CL=27202
parent
3067781a
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
36 additions
and
0 deletions
+36
-0
bug142.go
test/bugs/bug142.go
+31
-0
golden.out
test/golden.out
+5
-0
No files found.
test/bugs/bug142.go
0 → 100644
View file @
b8035ab5
// $G $D/$F.go && $L $F.$A && ./$A.out || echo BUG: bug142
// Copyright 2009 The Go Authors. All rights reserved.
// Use of this source code is governed by a BSD-style
// license that can be found in the LICENSE file.
package
main
func
panic1
(
s
string
)
bool
{
panic
(
s
);
}
func
main
()
{
x
:=
false
&&
panic1
(
"first"
)
&&
panic1
(
"second"
);
x
=
x
==
true
&&
panic1
(
"first"
)
&&
panic1
(
"second"
);
}
/*
; 6.out
second
panic PC=0x250f98
main·panic1+0x36 /Users/rsc/goX/test/bugs/bug142.go:6
main·panic1(0xae30, 0x0)
main·main+0x23 /Users/rsc/goX/test/bugs/bug142.go:10
main·main()
mainstart+0xf /Users/rsc/goX/src/runtime/amd64/asm.s:53
mainstart()
sys·Goexit /Users/rsc/goX/src/runtime/proc.c:124
sys·Goexit()
;
*/
test/golden.out
View file @
b8035ab5
...
...
@@ -121,6 +121,11 @@ bugs/bug140.go:6: syntax error near L1
bugs/bug140.go:7: syntax error near L2
BUG should compile
=========== bugs/bug142.go
second
panic PC=xxx
BUG: bug142
=========== fixedbugs/bug016.go
fixedbugs/bug016.go:7: constant -3 overflows uint
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment