public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/38245] [4.4 Regression] stack corruption when a call is removed but not the outgoing argument pushes
Date: Wed, 07 Jan 2009 06:34:00 -0000 [thread overview]
Message-ID: <20090107063410.22642.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38245-12544@http.gcc.gnu.org/bugzilla/>
------- Comment #20 from ebotcazou at gcc dot gnu dot org 2009-01-07 06:34 -------
> Most "interesting" libcalls for x86 -m32 probably are the DImode ones, and if
> subreg lowering does this for all arguments, we would have to update the
> REG_REP notes in the CALL_INSN, or do a lot of DSE-like work...
What about canonicalizing the modes in CALL_INSN_FUNCTION_USAGE to word mode
or smaller, like for hard registers? Would this make the DSE-like work more
or less trivial?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38245
next prev parent reply other threads:[~2009-01-07 6:34 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-24 4:09 [Bug c/38245] New: apparent improper segfault in compiler output regehr at cs dot utah dot edu
2008-11-24 9:03 ` [Bug rtl-optimization/38245] [4.4 Regression] " jakub at gcc dot gnu dot org
2008-11-24 9:12 ` ebotcazou at gcc dot gnu dot org
2008-11-27 17:39 ` jsm28 at gcc dot gnu dot org
2008-11-28 11:25 ` steven at gcc dot gnu dot org
2008-11-28 11:59 ` [Bug rtl-optimization/38245] [4.4 Regression] stack corruption when a call is removed but not the outgoing argument pushes ebotcazou at gcc dot gnu dot org
2008-11-28 14:14 ` jakub at gcc dot gnu dot org
2008-11-28 16:01 ` ebotcazou at gcc dot gnu dot org
2008-12-01 14:38 ` jakub at gcc dot gnu dot org
2008-12-02 17:48 ` jakub at gcc dot gnu dot org
2008-12-02 17:52 ` jakub at gcc dot gnu dot org
2008-12-05 10:29 ` ebotcazou at gcc dot gnu dot org
2008-12-05 11:08 ` jakub at gcc dot gnu dot org
2008-12-11 23:05 ` ebotcazou at gcc dot gnu dot org
2008-12-18 16:59 ` steven at gcc dot gnu dot org
2008-12-18 21:20 ` steven at gcc dot gnu dot org
2008-12-18 22:37 ` steven at gcc dot gnu dot org
2008-12-18 22:59 ` steven at gcc dot gnu dot org
2008-12-19 9:52 ` jakub at gcc dot gnu dot org
2008-12-19 10:43 ` jakub at gcc dot gnu dot org
2008-12-19 14:39 ` jakub at gcc dot gnu dot org
2008-12-20 9:58 ` steven at gcc dot gnu dot org
2009-01-07 6:34 ` ebotcazou at gcc dot gnu dot org [this message]
2009-01-12 16:19 ` jakub at gcc dot gnu dot org
2009-01-13 15:37 ` jakub at gcc dot gnu dot org
2009-01-15 8:08 ` jakub at gcc dot gnu dot org
2009-01-15 8:16 ` jakub at gcc dot gnu dot org
2009-01-30 22:36 ` hjl 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=20090107063410.22642.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).