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 target/39496] [4.2/4.3/4.4 Regression] GCC uses non-standard calling conventions for static functions with -O0.
Date: Wed, 18 Mar 2009 21:57:00 -0000	[thread overview]
Message-ID: <20090318215745.1433.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39496-16196@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from pinskia at gcc dot gnu dot org  2009-03-18 21:57 -------
We used to check flag_unit_at_a_time in this function:
  /* Use register calling convention for local functions when possible.  */
  if (decl && TREE_CODE (decl) == FUNCTION_DECL
      && flag_unit_at_a_time && !profile_flag)

Which meant it never worked for C++ in 3.4 and above , for C, it always worked
until 4.4 which removed the check.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39496


  parent reply	other threads:[~2009-03-18 21:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-18 21:10 [Bug c++/39496] New: GCC uses non-standard calling conventions, even " jimb at red-bean dot com
2009-03-18 21:12 ` [Bug c++/39496] " jimb at red-bean dot com
2009-03-18 21:14 ` [Bug target/39496] GCC uses non-standard calling conventions for static functions " pinskia at gcc dot gnu dot org
2009-03-18 21:32 ` [Bug target/39496] [4.2/4.3/4.4 Regression] " rguenth at gcc dot gnu dot org
2009-03-18 21:56 ` pinskia at gcc dot gnu dot org
2009-03-18 21:57 ` pinskia at gcc dot gnu dot org [this message]
2009-03-19  7:58 ` jakub at gcc dot gnu dot org
2009-03-19 10:26 ` jakub at gcc dot gnu dot org
2009-03-19 12:02 ` [Bug target/39496] [4.2/4.3 " jakub at gcc dot gnu dot org
2009-03-19 19:51 ` jimb at red-bean dot com
2009-03-31 21:11 ` [Bug target/39496] [4.3 " jsm28 at gcc dot gnu dot org
2009-04-22 13:30 ` rguenth at gcc dot gnu dot org
2009-04-22 15:02 ` rguenth at gcc dot gnu dot org
2009-04-22 15:02 ` rguenth 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=20090318215745.1433.qmail@sourceware.org \
    --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: link
Be 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).