public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: mrs@wrs.com To: gcc-gnats@gcc.gnu.org Subject: c++/5998: regression, all builtins disabled Date: Mon, 18 Mar 2002 12:36:00 -0000 [thread overview] Message-ID: <20020318203536.15882.qmail@sources.redhat.com> (raw) >Number: 5998 >Category: c++ >Synopsis: regression, all builtins disabled >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Mon Mar 18 12:36:01 PST 2002 >Closed-Date: >Last-Modified: >Originator: Mike Stump >Release: top of tree cvs >Organization: >Environment: sparc-sun-solaris2.7, affects all hosts/targets >Description: Mark recently put in: > /* In C++, we never create builtin functions whose name does not > begin with `__'. Users should be using headers to get prototypes > in C++. It would be nice if we could warn when `-fbuiltin' is > used explicitly, but we do not have that information. */ > flag_no_builtin = 1; this this is wrong. It disables all builtins, and causes performance regressions with C++ code: #include <memory.h> int a, b; int main() { memcpy(&a, &b, sizeof(a)); } for example. Also, alloca should not just disappear, it is a long standing extension, and disappearing it should be well thought out, not just done. See also http://gcc.gnu.org/ml/gcc/2002-03/msg00895.html for the mailing list traffic. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-03-18 20:36 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-03-18 12:36 mrs [this message] 2002-03-19 11:45 mmitchel 2002-03-29 12:44 mmitchel
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=20020318203536.15882.qmail@sources.redhat.com \ --to=mrs@wrs.com \ --cc=gcc-gnats@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).