public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Jim Wilson <wilson@tuliptree.org> To: wilson@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c/7871: ICE on legal code, global register variables problems Date: Sun, 06 Apr 2003 19:46:00 -0000 [thread overview] Message-ID: <20030406194600.31569.qmail@sources.redhat.com> (raw) The following reply was made to PR c/7871; it has been noted by GNATS. From: Jim Wilson <wilson@tuliptree.org> To: Richard Zidlicky <rz@linux-m68k.org> Cc: Richard Henderson <rth@redhat.com>, gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, wilson@gcc.gnu.org Subject: Re: c/7871: ICE on legal code, global register variables problems Date: 06 Apr 2003 15:37:51 -0400 On Wed, 2003-04-02 at 15:49, Richard Zidlicky wrote: > how does this differ from =C2=B4normal=C2=B4 global variables? Normal global variables are stored in memory instead of in registers. We don't add REG_NOTES and/or LOG_LINKS for values in memory like we do for registers. Also, most optimization passes known that memory is volatile across function calls, but they assume (call-saved) registers will be preserved. Thus we need special treatment for global register variables. > my application is still miscompiled with this patch.=20 OK, so we need more work here. > Tested only gcc-3.2, should this make any difference? No. I haven't had a chance to do any more work on this problem since my original message, and won't for a while. I'm in the middle of a 4000 km international move, and will be offline for the next week or two. Jim
next reply other threads:[~2003-04-06 19:46 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-06 19:46 Jim Wilson [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-02 14:16 Richard Zidlicky 2003-05-02 12:26 Richard Zidlicky 2003-05-01 6:06 Jim Wilson 2003-04-02 20:56 Richard Zidlicky 2003-03-10 5:16 Jim Wilson 2003-02-28 16:46 Jim Wilson 2003-02-28 5:56 Richard Henderson 2003-02-28 3:26 Jim Wilson 2003-02-28 3:02 wilson 2002-12-14 12:56 Richard Zidlicky 2002-09-09 14:36 Richard Zidlicky
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=20030406194600.31569.qmail@sources.redhat.com \ --to=wilson@tuliptree.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=wilson@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).