public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/65520] New: elaborated-type-specifiers and inaccessible injected-class-names
@ 2015-03-23  5:23 rs2740 at gmail dot com
  2015-03-23 10:07 ` [Bug c++/65520] " redi at gcc dot gnu.org
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: rs2740 at gmail dot com @ 2015-03-23  5:23 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65520

            Bug ID: 65520
           Summary: elaborated-type-specifiers and inaccessible
                    injected-class-names
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: rs2740 at gmail dot com

Repro:

struct A {};
struct B : private A {};
struct C : public B {
    struct A m_a; // error: A is the inaccessible injected-class-name
};

Per [basic.lookup.elab]/p2, the elaborated-type-specifier `struct A` should
cause an unqualified name lookup for `A`, and per [basic.lookup.unqual]/p7 the
name is first searched in C and its base classes, which should find the
inaccessible injected-class-name, rendering the code ill-formed.

Instead, GCC accepts this code. It is rejected by all versions of Clang I
tested (3.0 and later).


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug c++/65520] elaborated-type-specifiers and inaccessible injected-class-names
  2015-03-23  5:23 [Bug c++/65520] New: elaborated-type-specifiers and inaccessible injected-class-names rs2740 at gmail dot com
@ 2015-03-23 10:07 ` redi at gcc dot gnu.org
  2022-08-09  2:12 ` pinskia at gcc dot gnu.org
  2022-08-09  2:13 ` pinskia at gcc dot gnu.org
  2 siblings, 0 replies; 4+ messages in thread
From: redi at gcc dot gnu.org @ 2015-03-23 10:07 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65520

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |accepts-invalid
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2015-03-23
     Ever confirmed|0                           |1


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug c++/65520] elaborated-type-specifiers and inaccessible injected-class-names
  2015-03-23  5:23 [Bug c++/65520] New: elaborated-type-specifiers and inaccessible injected-class-names rs2740 at gmail dot com
  2015-03-23 10:07 ` [Bug c++/65520] " redi at gcc dot gnu.org
@ 2022-08-09  2:12 ` pinskia at gcc dot gnu.org
  2022-08-09  2:13 ` pinskia at gcc dot gnu.org
  2 siblings, 0 replies; 4+ messages in thread
From: pinskia at gcc dot gnu.org @ 2022-08-09  2:12 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65520

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |xmh970252187 at gmail dot com

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
*** Bug 106377 has been marked as a duplicate of this bug. ***

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug c++/65520] elaborated-type-specifiers and inaccessible injected-class-names
  2015-03-23  5:23 [Bug c++/65520] New: elaborated-type-specifiers and inaccessible injected-class-names rs2740 at gmail dot com
  2015-03-23 10:07 ` [Bug c++/65520] " redi at gcc dot gnu.org
  2022-08-09  2:12 ` pinskia at gcc dot gnu.org
@ 2022-08-09  2:13 ` pinskia at gcc dot gnu.org
  2 siblings, 0 replies; 4+ messages in thread
From: pinskia at gcc dot gnu.org @ 2022-08-09  2:13 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65520

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://gcc.gnu.org/bugzill
                   |                            |a/show_bug.cgi?id=29040

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
>From what I found while looking into PR 106377 :

I suspect this is the same issue as PR 29040. see bug 29040 comment #2 which
describes basically the same thing I found.

Note ICC warns about this code being done for compability reasons with cfront
too (basically the long history of GCC and even pre-standard C++ has left some
things like this around).

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2022-08-09  2:13 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-03-23  5:23 [Bug c++/65520] New: elaborated-type-specifiers and inaccessible injected-class-names rs2740 at gmail dot com
2015-03-23 10:07 ` [Bug c++/65520] " redi at gcc dot gnu.org
2022-08-09  2:12 ` pinskia at gcc dot gnu.org
2022-08-09  2:13 ` 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).