public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
* [Bug go/49889] New: Calling a function whose name is obscured by a local variable does not produce an error
@ 2011-07-28 18:36 rluble at gmail dot com
2011-08-04 4:08 ` [Bug go/49889] " ian at gcc dot gnu.org
2011-08-04 4:10 ` ian at airs dot com
0 siblings, 2 replies; 3+ messages in thread
From: rluble at gmail dot com @ 2011-07-28 18:36 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49889
Summary: Calling a function whose name is obscured by a local
variable does not produce an error
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Severity: minor
Priority: P3
Component: go
AssignedTo: ian@airs.com
ReportedBy: rluble@gmail.com
Created attachment 24859
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=24859
Small program exhibiting the mentioned error
When calling a function whose name is obscured by a local variable on a *tuple
assignment* statement (as in the example below) no error is produced and the
generated code does not have the function call.
func test(a int) (int, int) {
b:=a+1
return b,a
}
func main() {
test, a := 1, 1
c,d := 1,1
c,d = test(a)
}
The expected behaviour is to produce an error.
^ permalink raw reply [flat|nested] 3+ messages in thread* [Bug go/49889] Calling a function whose name is obscured by a local variable does not produce an error 2011-07-28 18:36 [Bug go/49889] New: Calling a function whose name is obscured by a local variable does not produce an error rluble at gmail dot com @ 2011-08-04 4:08 ` ian at gcc dot gnu.org 2011-08-04 4:10 ` ian at airs dot com 1 sibling, 0 replies; 3+ messages in thread From: ian at gcc dot gnu.org @ 2011-08-04 4:08 UTC (permalink / raw) To: gcc-bugs http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49889 --- Comment #1 from ian at gcc dot gnu.org <ian at gcc dot gnu.org> 2011-08-04 04:08:35 UTC --- Author: ian Date: Thu Aug 4 04:08:29 2011 New Revision: 177310 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=177310 Log: PR go/49889 gccgo : Fixed bug 49889. Now the compiler emits a proper error when a function called in a tuple assignment statement can not be typed as a function. Modified: trunk/gcc/go/gofrontend/expressions.cc ^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug go/49889] Calling a function whose name is obscured by a local variable does not produce an error 2011-07-28 18:36 [Bug go/49889] New: Calling a function whose name is obscured by a local variable does not produce an error rluble at gmail dot com 2011-08-04 4:08 ` [Bug go/49889] " ian at gcc dot gnu.org @ 2011-08-04 4:10 ` ian at airs dot com 1 sibling, 0 replies; 3+ messages in thread From: ian at airs dot com @ 2011-08-04 4:10 UTC (permalink / raw) To: gcc-bugs http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49889 Ian Lance Taylor <ian at airs dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |FIXED --- Comment #2 from Ian Lance Taylor <ian at airs dot com> 2011-08-04 04:09:00 UTC --- Fixed in mainline. ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2011-08-04 4:10 UTC | newest] Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2011-07-28 18:36 [Bug go/49889] New: Calling a function whose name is obscured by a local variable does not produce an error rluble at gmail dot com 2011-08-04 4:08 ` [Bug go/49889] " ian at gcc dot gnu.org 2011-08-04 4:10 ` ian at airs dot com
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).