public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steven at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/15579] [3.5 Regression] always_inline ignored at -O0
Date: Thu, 03 Jun 2004 23:03:00 -0000 [thread overview]
Message-ID: <20040603230301.15341.qmail@sourceware.org> (raw)
In-Reply-To: <20040521233457.15579.janis187@us.ibm.com>
------- Additional Comments From steven at gcc dot gnu dot org 2004-06-03 23:02 -------
And I say it is broken for all languages other than C.
This only works because even at -O0 or with -fno-inline, C actually has
flag_inline_trees set to 1. The C++ front end does not, and that is the
correct behavior in my opinion.
Actually I was just working on a patch for this (as part of killing that
detestable flag_inline_trees/flag_really_no_inline hack). So I'm taking
responsibility for this bug in the hope that it will go away with that
patch I'm working on ;-)
--
What |Removed |Added
----------------------------------------------------------------------------
BugsThisDependsOn| |7257
AssignedTo|unassigned at gcc dot gnu |steven at gcc dot gnu dot
|dot org |org
Status|NEW |ASSIGNED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15579
next prev parent reply other threads:[~2004-06-03 23:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-22 22:05 [Bug c++/15579] New: tree-ssa regression for C++ altivec tests janis187 at us dot ibm dot com
2004-05-22 22:36 ` [Bug tree-optimization/15579] [3.5 Regression] always_inline ignored at -O0 pinskia at gcc dot gnu dot org
2004-05-22 22:52 ` [Bug middle-end/15579] " janis187 at us dot ibm dot com
2004-06-03 23:03 ` steven at gcc dot gnu dot org [this message]
2004-09-12 0:43 ` pinskia at gcc dot gnu dot org
2004-11-27 0:51 ` [Bug middle-end/15579] [4.0 " steven 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=20040603230301.15341.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).