public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/26034] New: [4.0/4.1/4.2 Regression] gcc uses way too much stack space for this code Date: Mon, 30 Jan 2006 14:44:00 -0000 [thread overview] Message-ID: <bug-26034-6528@http.gcc.gnu.org/bugzilla/> (raw) Take the following code: typedef struct a { int f[1000]; void g(); a operator=(const a&); } a; a f(void); int g(void) { a t; t = f(); } in 4.0, we use 20008 bytes for the stack. In 4.2 and 4.1, we use 16024 bytes for the stack. In 3.4 and 3.3, we use 12024 bytes for the stack. This is semi reduced from PR 25505 (there is another case in there already). -- Summary: [4.0/4.1/4.2 Regression] gcc uses way too much stack space for this code Product: gcc Version: 4.2.0 Status: UNCONFIRMED Keywords: missed-optimization Severity: normal Priority: P3 Component: middle-end AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: pinskia at gcc dot gnu dot org OtherBugsDependingO 25505 nThis: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26034
next reply other threads:[~2006-01-30 14:44 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-01-30 14:44 pinskia at gcc dot gnu dot org [this message] 2006-02-03 19:25 ` [Bug middle-end/26034] " pinskia at gcc dot gnu dot org 2006-02-14 8:58 ` mmitchel at gcc dot gnu dot org 2006-02-14 15:12 ` [Bug middle-end/26034] [4.0 " rguenth at gcc dot gnu dot org 2006-03-11 3:19 ` mmitchel at gcc dot gnu dot org 2007-02-03 16:15 ` gdr 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=bug-26034-6528@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: 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).