From: Denis Zaitsev <zzz@anda.ru>
To: Andrew Pinski <pinskia@physics.uc.edu>
Cc: gcc@gcc.gnu.org, linux-gcc@vger.kernel.org
Subject: Re: [BUG] GCC 3.4-20041224: __attribute__ ((regparm)) misbehaviour
Date: Tue, 28 Dec 2004 08:54:29 +0500 [thread overview]
Message-ID: <20041228085429.D1437@natasha.ward.six> (raw)
In-Reply-To: <83F66334-5883-11D9-9D38-000A95D692F4@physics.uc.edu>; from pinskia@physics.uc.edu on Mon, Dec 27, 2004 at 10:49:46PM -0500
On Mon, Dec 27, 2004 at 10:49:46PM -0500, Andrew Pinski wrote:
>
> On Dec 27, 2004, at 10:44 PM, Denis Zaitsev wrote:
>
> > This program:
> >
> >
> > static
> > int x(int y)
> > __attribute__ ((regparm(1)));
> >
> > static
> > int x(int y)
> > {
> > return y;
> > }
> >
>
> No this is not a bug. You need regparm attribute on the function
> definition too.
Hmm... Is it regparm-only related? And is it something new though?
GCC 3.3.x doesnt show this behaviour.
next prev parent reply other threads:[~2004-12-28 3:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-28 3:44 [BUG] GCC 3.4-20041224: __attribute__ ((regparm)) misbehaviour Denis Zaitsev
2004-12-28 3:49 ` Andrew Pinski
2004-12-28 3:54 ` Denis Zaitsev [this message]
2004-12-28 3:57 ` Andrew Pinski
2004-12-28 4:04 ` Denis Zaitsev
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=20041228085429.D1437@natasha.ward.six \
--to=zzz@anda.ru \
--cc=gcc@gcc.gnu.org \
--cc=linux-gcc@vger.kernel.org \
--cc=pinskia@physics.uc.edu \
/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 NNTP newsgroup(s).