public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/54068] Compiler passes wrong argument to function when using optimize attribute with -O3
Date: Sun, 08 Aug 2021 22:22:20 +0000 [thread overview]
Message-ID: <bug-54068-4-EsMpkC5OgC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54068-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54068
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |DUPLICATE
Status|NEW |RESOLVED
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
251901a027bf (Jakub Jelinek 2014-02-06 11:54:20 +0100 6619)
/* Caller and callee must agree on the calling convention, so
251901a027bf (Jakub Jelinek 2014-02-06 11:54:20 +0100 6620)
checking here just optimize means that with
251901a027bf (Jakub Jelinek 2014-02-06 11:54:20 +0100 6621)
__attribute__((optimize (...))) caller could use regparm convention
251901a027bf (Jakub Jelinek 2014-02-06 11:54:20 +0100 6622)
and callee not, or vice versa. Instead look at whether the callee
251901a027bf (Jakub Jelinek 2014-02-06 11:54:20 +0100 6623)
is optimized or not. */
So dup of bug 60062.
*** This bug has been marked as a duplicate of bug 60062 ***
prev parent reply other threads:[~2021-08-08 22:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-22 23:39 [Bug c/54068] New: Compiler passes wrong argument to function when using -O3 and inline vogu00 at gmail dot com
2012-07-22 23:46 ` [Bug middle-end/54068] Compiler passes wrong argument to function when using optimize attribute with -O3 pinskia at gcc dot gnu.org
2012-07-23 8:26 ` rguenth at gcc dot gnu.org
2012-07-23 10:17 ` steven at gcc dot gnu.org
2021-08-08 22:22 ` pinskia at gcc dot gnu.org [this message]
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=bug-54068-4-EsMpkC5OgC@http.gcc.gnu.org/bugzilla/ \
--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).