public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "yuri at tsoft dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/19661] New: many redundant atexit calls emitted into the executable for static objects with empty destructors Date: Thu, 27 Jan 2005 22:24:00 -0000 [thread overview] Message-ID: <20050127222428.19661.yuri@tsoft.com> (raw) When some object having empty destructor is declared as static in the local context of some function g++ still inserts <atexit> call with the empty handler like <__tcf_0> below. It may seem like minor issue but redundant instructions increase chances for I-cache misses and worthen processor pipeline. Yuri 08048800 <__tcf_0>: 8048800: 55 push %ebp 8048801: 89 e5 mov %esp,%ebp 8048803: 5d pop %ebp 8048804: c3 ret --testcase-- begin 644 case-empty-atexit.tgz M'XL(`.1G^4$``^V6VVJ#0!"&O=ZG&-*;))!D/:Q>)!1"GV31:2.83=`U&$KZ M[!U-BI)#<U%)"YT/85?\]Z#C/[.Q+G""ZZW=3[3%*K4SIW>D#&2D%+5*JLBG M5DHW4$U[PG&E&X5>Z(>^YTC7#X/(`=7_5BXI"ZMS`&=?YNEWN@1WF&VVC]C2 M(XDOXE]-7WI>0[I2AD%P,_X4^:_XUW\`Z0//"QV0/>_C*O\\_D(\I2;.R@1A M4$U7`R&PLI@;V&W2!,H"AZ.Y$/2-;!K#$C3=B+5.S7`$[P(@WI06%@L8H*%1 M@[J+)LGF].@TMJ/)4.^PHSF(WWY[YIK_5SVO<<__7NM_GZ2-_U7$_G\$'?\O MTDUA<]3K9U$6J7D#H]=8;'6,4-BDR0)Y&5O*`K7SEW4&:+V]I*XY"C!I/0X' MDC:IY-6<#Z`$<:[\.,XZ&W=D"5Y..YZ1_##G_/%CKOA_0H'I]0QPM_Y+U=;_ M*"*]HHO]_PANE?]CJ6\/`8WGN\<``#VM/<UEG&$8AF$8AF$8AF$8AF$8AF$8 -AF'^#)_;GM5=`"@````` ` end -- Summary: many redundant atexit calls emitted into the executable for static objects with empty destructors Product: gcc Version: 3.4.2 Status: UNCONFIRMED Severity: normal Priority: P2 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: yuri at tsoft dot com CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: n/a GCC target triplet: n/a http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19661
next reply other threads:[~2005-01-27 22:24 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-01-27 22:24 yuri at tsoft dot com [this message] 2005-01-28 1:08 ` [Bug c++/19661] unnecessary atexit calls emitted " bangerth at dealii dot org 2005-01-28 1:22 ` [Bug middle-end/19661] " pinskia at gcc dot gnu dot org 2005-01-28 1:26 ` [Bug c++/19661] " yuri at tsoft dot com 2005-01-28 1:46 ` [Bug middle-end/19661] " pinskia at gcc dot gnu dot org 2005-01-28 17:02 ` [Bug c++/19661] " bangerth at dealii dot org 2005-01-28 18:53 ` [Bug middle-end/19661] " pinskia at gcc dot gnu dot org 2005-01-28 19:11 ` bangerth at dealii dot org 2005-09-24 17:43 ` [Bug tree-optimization/19661] " pinskia at gcc dot gnu dot org
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=20050127222428.19661.yuri@tsoft.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).