public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia@physics.uc.edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug optimization/8361] [3.3/3.4 regression] C++ compile-time performance regression Date: Fri, 13 Jun 2003 19:29:00 -0000 [thread overview] Message-ID: <20030613192907.26538.qmail@sources.redhat.com> (raw) In-Reply-To: <20021025133601.8361.pfeifer@dbai.tuwien.ac.at> PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=8361 ------- Additional Comments From pinskia@physics.uc.edu 2003-06-13 19:29 ------- I found one of the problems with walking the trees too much, finish_function calls calls_setjmp_p when inlining is turned off which is not needed. This was added with this patch: 1999-12-05 Mark Mitchell <mark@codesourcery.com> * decl.c (init_decl_processing): Set flag_inline_trees if !flag_no_inline. * cp-tree.h (calls_setjmp_p): Declare. * decl.c (finish_function): Mark functions that call setjmp as uninlinable. * optimize.c (calls_setjmp_r): New function. (calls_setjmp_p): Likewise. There is an easy fix for this one is not to call setjmp if flag_inline_trees is non-zero.
next prev parent reply other threads:[~2003-06-13 19:29 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20021025133601.8361.pfeifer@dbai.tuwien.ac.at> 2003-06-08 18:51 ` pinskia@physics.uc.edu 2003-06-13 19:00 ` pinskia@physics.uc.edu 2003-06-13 19:29 ` pinskia@physics.uc.edu [this message] 2003-06-13 19:47 ` s.bosscher@student.tudelft.nl 2003-06-13 19:52 ` pinskia@physics.uc.edu 2003-06-19 22:02 ` s dot bosscher at student dot tudelft dot nl 2003-06-20 21:17 ` dann at godzilla dot ics dot uci dot edu 2003-06-24 23:04 ` pinskia at physics dot uc dot edu 2003-07-11 23:42 ` steven at gcc dot gnu dot org 2003-07-12 20:06 ` steven at gcc dot gnu dot org 2003-07-16 11:29 ` steven at gcc dot gnu dot org 2003-07-18 15:27 ` steven at gcc dot gnu dot org 2003-07-23 22:50 ` mmitchel at gcc dot gnu dot org 2003-07-23 23:11 ` gdr at integrable-solutions dot net 2003-07-23 23:24 ` pinskia at physics dot uc dot edu 2003-07-23 23:38 ` gerald at gcc dot gnu dot org 2003-07-24 14:29 ` bangerth at dealii dot org [not found] <20021025133601.8361.gerald@pfeifer.com> 2003-10-16 2:39 ` mmitchel at gcc dot gnu dot org 2003-12-29 16:23 ` steven at gcc dot gnu dot org 2004-01-02 2:31 ` giovannibajo at libero dot it 2004-01-14 3:22 ` pinskia at gcc dot gnu dot org 2003-05-23 15:37 pinskia@physics.uc.edu -- strict thread matches above, loose matches on Subject: below -- 2003-05-23 15:32 pinskia@physics.uc.edu
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=20030613192907.26538.qmail@sources.redhat.com \ --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: 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).