public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Gwenole Beauchesne <gbeauchesne@mandrakesoft.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/6323: GCC 3.1 regression from previous snapshot Date: Tue, 16 Apr 2002 06:56:00 -0000 [thread overview] Message-ID: <20020416135603.19755.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/6323; it has been noted by GNATS. From: Gwenole Beauchesne <gbeauchesne@mandrakesoft.com> To: gcc-gnats@gcc.gnu.org, <gcc-prs@gcc.gnu.org>, <mark@codesourcery.com>, <gcc-bugs@gcc.gnu.org>, <nobody@gcc.gnu.org>, <jason@redhat.com>, <roger@eyesopen.com> Cc: Subject: Re: optimization/6323: GCC 3.1 regression from previous snapshot Date: Tue, 16 Apr 2002 15:49:09 +0200 (CEST) Hi, The following patch appears to have caused the regression: <http://gcc.gnu.org/ml/gcc-patches/2002-03/msg01513.html> 2002-03-28 Roger Sayle <roger@eyesopen.com> PR c++/5998: * decl.c (cxx_init_decl_processing): Re-enable built-in functions in the g++ front-end. (duplicate_decl): Allow redefinition of anticipated built-ins. Fix inlining problem by over-writing the old DECL_RTL. (lookup_namespace_name): Fail to find an identifier in the specified namespace if its still anticipated. (builtin_function_1): New function split out from builtin_function to create a builtin in the current namespace with given context. (builtin_function): Call builtin_function_1 to define the appropriate builtins in both the std and global namespaces. (select_decl): Don't test for anticipated decls here. (unqualified_namespace_lookup): Instead ignore them whilst searching through scopes and namespaces. * decl2.c (do_nonmember_using_decl): If a using declaration specifies an anticipated built-in function, mark it as no longer anticipated in that scope. (ambiguous_decl): Avoid resolving to an anticipated decl. * lex.c (do_scoped_id): Fail to find an identifier in the global namespace if its still anticipated. Bye, Gwenole.
next reply other threads:[~2002-04-16 13:56 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-04-16 6:56 Gwenole Beauchesne [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-04-18 10:28 mmitchel 2002-04-17 0:06 Gwenole Beauchesne 2002-04-16 18:55 rth 2002-04-16 18:11 rth 2002-04-16 6:26 Gwenole Beauchesne 2002-04-16 6:06 gbeauchesne
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=20020416135603.19755.qmail@sources.redhat.com \ --to=gbeauchesne@mandrakesoft.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).