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 target/30271] -mstrict-align can an store extra for struct agrument passing Date: Thu, 11 Dec 2008 04:44:00 -0000 [thread overview] Message-ID: <20081211044242.24730.qmail@sourceware.org> (raw) In-Reply-To: <bug-30271-6528@http.gcc.gnu.org/bugzilla/> ------- Comment #8 from pinskia at gcc dot gnu dot org 2008-12-11 04:42 ------- So the problem with the stores here is that the base is arg_pointer_rtx which is still a frame pointer related offset. I think the same can be said is true of stack_pointer_rtx too. We only set frame_related for frame_pointer_rtx and hard_frame_pointer_rtx but arg_pointer_rtx will become a frame pointer later one too. The only issue is that there might not be correct dependencies with respect of arg_pointer_rtx. Kenny, Do you agree? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30271
next prev parent reply other threads:[~2008-12-11 4:44 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-12-21 2:49 [Bug target/30271] New: -mstrict-align can cause bad code generation " pinskia at gcc dot gnu dot org 2006-12-21 22:23 ` [Bug target/30271] " pinskia at gcc dot gnu dot org 2007-07-24 2:14 ` pinskia at gcc dot gnu dot org 2007-07-24 2:15 ` pinskia at gcc dot gnu dot org 2007-10-15 21:30 ` pinskia at gcc dot gnu dot org 2007-10-15 21:36 ` [Bug target/30271] -mstrict-align can an extra " pinskia at gcc dot gnu dot org 2007-10-15 21:50 ` pinskia at gcc dot gnu dot org 2007-10-29 14:09 ` zadeck at naturalbridge dot com 2007-10-30 0:38 ` zadeck at naturalbridge dot com 2008-12-11 4:44 ` pinskia at gcc dot gnu dot org [this message] 2008-12-15 15:34 ` [Bug target/30271] -mstrict-align can an store " zadeck at naturalbridge dot com 2008-12-16 2:09 ` pinskia at gcc dot gnu dot org 2008-12-29 23:53 ` pinskia at gcc dot gnu dot org [not found] <bug-30271-4@http.gcc.gnu.org/bugzilla/> 2020-05-21 6:15 ` luoxhu at gcc dot gnu.org 2023-12-08 11:01 ` guojiufu at gcc dot gnu.org 2023-12-19 5:18 ` cvs-commit at gcc dot gnu.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=20081211044242.24730.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: linkBe 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).