public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: pinskia@physics.uc.edu
To: gcc-gnats@gcc.gnu.org
Subject: c/10320: [3.4 regression] gcc 3.4 gets rid of static inline function that does not get inlined
Date: Sun, 06 Apr 2003 16:46:00 -0000	[thread overview]
Message-ID: <20030406163614.32457.qmail@sources.redhat.com> (raw)


>Number:         10320
>Category:       c
>Synopsis:       [3.4 regression] gcc 3.4 gets rid of static inline function that does not get inlined
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Apr 06 16:46:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Andrew Pinski
>Release:        gcc version 3.4 20030406 (experimental)
>Organization:
>Environment:
i686-pc-linux-gnu and powerpc-apple-darwin6.4, it should not matter.
>Description:
If a function that is declared inline is defined without inline after where it is called, the function is not inlined and is not emited.
Note with -funit-at-a-time or -finline-functions, it works.
It does not work at -O0, -O1, or -O2 or -O3 -fno-unit-at-a-time -fno-inline-functions.

Note this causes ssa-branch bootstrap failure on powerpc-apple-darwin6.4.
Note this also works right with `gcc version 3.2.1 20021207 (Red Hat Linux 8.0 3.2.1-2)' and `Apple Computer, Inc. GCC version 1175, based on gcc version 3.1 20020420 (prerelease)' and `gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)' so this is regression.
>How-To-Repeat:
compile and link and run (try at least) the following source:
static inline void temp();
int main()
{
        temp();
        return 0;
}
static void temp(){}
>Fix:
Do not know.
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2003-04-06 16:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-06 16:46 pinskia [this message]
2003-04-06 17:16 Diego Novillo
2003-04-06 17:26 Andrew Pinski
2003-05-15  5:31 bangerth

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=20030406163614.32457.qmail@sources.redhat.com \
    --to=pinskia@physics.uc.edu \
    --cc=gcc-gnats@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).