public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/53434] New: Compiler decides declaration/expression ambiguity too soon.
@ 2012-05-21 12:43 james.kanze at gmail dot com
2012-05-26 23:48 ` [Bug c++/53434] " pinskia at gcc dot gnu.org
2021-07-24 2:36 ` pinskia at gcc dot gnu.org
0 siblings, 2 replies; 3+ messages in thread
From: james.kanze at gmail dot com @ 2012-05-21 12:43 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53434
Bug #: 53434
Summary: Compiler decides declaration/expression ambiguity too
soon.
Classification: Unclassified
Product: gcc
Version: 4.6.3
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: james.kanze@gmail.com
Created attachment 27459
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27459
Source code for very simple program showing the bug.
This may be the same as 37213, but the context is somewhat different. When I
compile (simply g++ -c <filename>), I get the following error message:
bugInGcc.cc: In function 'void f()':
bugInGcc.cc:20:39: error: size of array has non-integral type 'const char [2]'
bugInGcc.cc:20:39: error: 'parameter' declared as function returning an array
Apparently, g++ is deciding in favor of declaration after seeing C()["a"],
despite the fact that a declaration cannot be followed by a . operator.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug c++/53434] Compiler decides declaration/expression ambiguity too soon.
2012-05-21 12:43 [Bug c++/53434] New: Compiler decides declaration/expression ambiguity too soon james.kanze at gmail dot com
@ 2012-05-26 23:48 ` pinskia at gcc dot gnu.org
2021-07-24 2:36 ` pinskia at gcc dot gnu.org
1 sibling, 0 replies; 3+ messages in thread
From: pinskia at gcc dot gnu.org @ 2012-05-26 23:48 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53434
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |rejects-valid
Status|UNCONFIRMED |NEW
Last reconfirmed| |2012-05-26
Depends on| |29834
Ever Confirmed|0 |1
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> 2012-05-26 22:44:04 UTC ---
Most likely a dup of bug 29834 (well at least related to it).
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug c++/53434] Compiler decides declaration/expression ambiguity too soon.
2012-05-21 12:43 [Bug c++/53434] New: Compiler decides declaration/expression ambiguity too soon james.kanze at gmail dot com
2012-05-26 23:48 ` [Bug c++/53434] " pinskia at gcc dot gnu.org
@ 2021-07-24 2:36 ` pinskia at gcc dot gnu.org
1 sibling, 0 replies; 3+ messages in thread
From: pinskia at gcc dot gnu.org @ 2021-07-24 2:36 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53434
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed|2012-05-26 00:00:00 |2021-7-23
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Self contained testcase without include:
struct d
{
d(const char*);
};
class S
{
public:
d getString( d const& ) const;
};
class C
{
public:
C();
S const& operator[]( d const& ) const;
};
void
f()
{
static d const s(C()["a"].getString("b"));
}
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2021-07-24 2:36 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-05-21 12:43 [Bug c++/53434] New: Compiler decides declaration/expression ambiguity too soon james.kanze at gmail dot com
2012-05-26 23:48 ` [Bug c++/53434] " pinskia at gcc dot gnu.org
2021-07-24 2:36 ` pinskia at gcc dot gnu.org
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).