public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Eric Botcazou <ebotcazou@libertysurf.fr> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: target/6882: [SPARC] Useless stack adjustment code Date: Mon, 31 Mar 2003 14:36:00 -0000 [thread overview] Message-ID: <20030331141601.802.qmail@sources.redhat.com> (raw) The following reply was made to PR target/6882; it has been noted by GNATS. From: Eric Botcazou <ebotcazou@libertysurf.fr> To: Hans-Peter Nilsson <hp@bitrange.com> Cc: dann@godzilla.ics.uci.edu, <gcc-bugs@gcc.gnu.org>, <nobody@gcc.gnu.org>, <gcc-gnats@gcc.gnu.org> Subject: Re: target/6882: [SPARC] Useless stack adjustment code Date: Mon, 31 Mar 2003 16:07:38 +0200 > Now you're arguing about the *value of the optimization*. > I was arguing about *closing the PR for the wrong reason*. Well, you only asked me to give a specific reason for the adjustment code. I agreed that there appears to be no compelling reason for it. But the problem is that the code is emitted anyway. So IMHO the right question is rather: are there strong enough reasons for removing it? Therefore I gave my opinion on this latter question. > Having said that, let's continue to the *new* discussion. You > can't optimize out the call from other translation units. Not > being a SPARC maintainer I won't try to judge on the benefit, > but it looks simple enough and seems worthwhile. C++ tends to > generate a lot of small trivial functions. Maybe. My impression is that, if the optimization was that simple and that worthwhile, it would already have been implemented. But I'm not a SPARC maintainer either, so... -- Eric Botcazou
next reply other threads:[~2003-03-31 14:16 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-31 14:36 Eric Botcazou [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-31 12:46 Hans-Peter Nilsson 2003-03-31 9:47 Falk Hueffner 2003-03-31 8:56 Eric Botcazou 2003-03-31 5:06 hp 2003-03-31 4:18 Hans-Peter Nilsson 2003-03-29 9:51 ebotcazou
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=20030331141601.802.qmail@sources.redhat.com \ --to=ebotcazou@libertysurf.fr \ --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).