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/32492] [4.3 Regression] attribute always_inline  ->  sorry, unimplemented: recursive inlining
Date: Tue, 26 Jun 2007 14:53:00 -0000	[thread overview]
Message-ID: <20070626145325.7518.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32492-8535@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from pinskia at gcc dot gnu dot org  2007-06-26 14:53 -------
I am going to change the component as middle-end while someone figures out if
we want to promote in the front-ends or later on.  I say we want to promote in
front-ends rather than later on because we get more information about the how
the arguments would look like (and we might lose some info otherwise).


-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |blocker
          Component|c                           |middle-end


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


  parent reply	other threads:[~2007-06-26 14:53 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-25 10:01 [Bug c++/32492] New: " wouter dot vermaelen at scarlet dot be
2007-06-26 10:32 ` [Bug c++/32492] [4.3 Regression] " rguenth at gcc dot gnu dot org
2007-06-26 15:16   ` Daniel Jacobowitz
2007-06-26 12:14 ` mark at codesourcery dot com
2007-06-26 14:31 ` pinskia at gcc dot gnu dot org
2007-06-26 14:39 ` [Bug c/32492] " pinskia at gcc dot gnu dot org
2007-06-26 14:51 ` pinskia at gcc dot gnu dot org
2007-06-26 14:53 ` pinskia at gcc dot gnu dot org [this message]
2007-06-26 15:03 ` [Bug middle-end/32492] " rguenther at suse dot de
2007-06-26 16:30 ` drow at gcc dot gnu dot org
2007-06-26 20:46 ` rguenth at gcc dot gnu dot org
2007-06-26 21:07 ` rguenth at gcc dot gnu dot org
2007-06-26 21:25 ` rguenth at gcc dot gnu dot org
2007-06-26 21:33 ` pinskia at gcc dot gnu dot org
2007-06-26 21:55 ` rguenther at suse dot de
2007-06-26 21:59   ` Andrew Pinski
2007-06-26 21:59 ` pinskia at gmail dot com
2007-06-27 14:01 ` rguenth at gcc dot gnu dot org
2007-06-27 15:05 ` rguenth at gcc dot gnu dot org
2008-06-11 10:07 ` josep dot m dot perez at bsc dot es
2008-06-16  9:24 ` josep dot m dot perez at bsc dot es

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=20070626145325.7518.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).