public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zhouzhouyi at ercist dot iscas dot ac dot cn" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/31886] (different from bug report c/31077 and 29241) C handling of always_inline attribute error and a solution
Date: Thu, 10 May 2007 03:43:00 -0000 [thread overview]
Message-ID: <20070510034344.19191.qmail@sourceware.org> (raw)
In-Reply-To: <bug-31886-14209@http.gcc.gnu.org/bugzilla/>
------- Comment #3 from zhouzhouyi at ercist dot iscas dot ac dot cn 2007-05-10 04:43 -------
Subject: Re: (different from bug report c/31077 and 29241) C
handling of always_inline attribute error and a solution
heh, pinkia, take a look at my solution1
On 10 May 2007 03:41:06 -0000
"zhouzhouyi at ercist dot iscas dot ac dot cn" <gcc-bugzilla@gcc.gnu.org>
wrote:
>
>
> ------- Comment #2 from zhouzhouyi at ercist dot iscas dot ac dot cn 2007-05-10 04:41 -------
> Subject: Re: (different from bug report c/31077 and 29241) C
> handling of always_inline attribute error and a solution
>
> Dear pinskia,
> If you lookup my solution current handling of conditions
> for optimize_inline_calls in tree_rest_of_compilation is obvious
> not good.
> Sincerely yours
> Zhouyi Zhou
> On 10 May 2007 03:19:10 -0000
> "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> wrote:
>
> >
> >
> > ------- Comment #1 from pinskia at gcc dot gnu dot org 2007-05-10 04:19 -------
> > I don't think this is a bug. The documentation for always inline says:
> > "For functions declared inline, this attribute inlines the function even if no
> > optimization level was specified."
> >
> > That quote is from:
> > http://gcc.gnu.org/onlinedocs/gcc-4.1.2/gcc/Function-Attributes.html
> > And it is also in:
> > http://gcc.gnu.org/onlinedocs/gcc-4.0.2/gcc/Function-Attributes.html
> >
> >
> > alloc_null_binding is not declared inline so how do you think GCC will inline
> > this function?
> >
> >
> > --
> >
> > pinskia at gcc dot gnu dot org changed:
> >
> > What |Removed |Added
> > ----------------------------------------------------------------------------
> > Status|UNCONFIRMED |WAITING
> > Summary|(different from bug report |(different from bug report
> > |c/31077 and 29241) C |c/31077 and 29241) C
> > |handling of always_inline |handling of always_inline
> > |attribute error and a |attribute error and a
> > |solution |solution
> >
> >
> > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31886
> >
> > ------- You are receiving this mail because: -------
> > You reported the bug, or are watching the reporter.
> >
>
>
> --
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31886
>
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
>
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31886
next prev parent reply other threads:[~2007-05-10 3:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-10 3:07 [Bug c/31886] New: " zhouyi04 at ios dot cn
2007-05-10 3:19 ` [Bug c/31886] " pinskia at gcc dot gnu dot org
2007-05-10 3:41 ` zhouzhouyi at ercist dot iscas dot ac dot cn
2007-05-10 3:43 ` zhouzhouyi at ercist dot iscas dot ac dot cn [this message]
2007-05-10 4:33 ` zhouyi04 at ios dot cn
2007-05-10 10:04 ` rguenth at gcc dot gnu dot org
2007-08-02 17:18 ` rob1weld at aol dot com
2007-08-02 17:24 ` rob1weld at aol dot com
2007-08-06 6:45 ` rob1weld at aol dot com
2007-08-06 8:41 ` zhouyi04 at ios dot cn
2007-08-20 7:58 ` rguenth at gcc dot gnu dot org
2009-01-13 22:10 ` rob1weld at aol dot com
2009-01-13 22:41 ` 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=20070510034344.19191.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).