public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/113830] GCC accepts invalid code when instantiating the local class inside a function
Date: Thu, 08 Feb 2024 13:53:12 +0000	[thread overview]
Message-ID: <bug-113830-4-Ektw00HFgt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113830-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
(In reply to Bo Wang from comment #4)
> (In reply to Marek Polacek from comment #2)
> > Bug 66900 is somewhat related in that we also allow int::j.
> 
> I believe these two bugs have different root causes. Bug 113830 should be
> due to not instantiating default arguments inside the template function,
> especially in instantiating a local class. While Bug 66900 does not have
> this issue.

Yes, I'm saying they are related, not dups.

  parent reply	other threads:[~2024-02-08 13:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-08 12:41 [Bug c++/113830] New: " wangbopku15 at gmail dot com
2024-02-08 13:01 ` [Bug c++/113830] " redi at gcc dot gnu.org
2024-02-08 13:08 ` mpolacek at gcc dot gnu.org
2024-02-08 13:24 ` wangbopku15 at gmail dot com
2024-02-08 13:38 ` wangbopku15 at gmail dot com
2024-02-08 13:42 ` jakub at gcc dot gnu.org
2024-02-08 13:53 ` mpolacek at gcc dot gnu.org [this message]
2024-02-08 14:14 ` wangbopku15 at gmail dot com
2024-02-08 15:01 ` redi at gcc dot gnu.org
2024-02-08 15:10 ` wangbopku15 at gmail dot com
2024-02-08 15:36 ` jakub at gcc dot gnu.org
2024-02-08 19:08 ` wangbopku15 at gmail dot com
2024-02-08 19:47 ` harald at gigawatt dot nl
2024-02-09  2:44 ` wangbopku15 at gmail dot com
2024-02-09  9:26 ` harald at gigawatt dot nl

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-113830-4-Ektw00HFgt@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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).