public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rearnsha at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/38644] Optimization flag -O1 -fschedule-insns2 causes wrong code Date: Tue, 22 Dec 2009 11:16:00 -0000 [thread overview] Message-ID: <20091222111641.28673.qmail@sourceware.org> (raw) In-Reply-To: <bug-38644-17122@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from rearnsha at gcc dot gnu dot org 2009-12-22 11:16 ------- IMO this is a generic bug in the scheduler. The code in sched-deps.c should note that STACK_POINTER_RTX is being changed and insert a memory barrier that prevents migration of stack-related memory accesses across the change. Of course, determining what memory accesses are stack-related is quite hard, and it may be that all memory accesses in the same address space as the stack will need to be restricted. -- rearnsha at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Component|target |rtl-optimization Last reconfirmed|2009-03-17 00:03:45 |2009-12-22 11:16:40 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38644
next prev parent reply other threads:[~2009-12-22 11:16 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-12-27 22:11 [Bug c/38644] New: " davejmurphy at me dot com 2008-12-27 22:11 ` [Bug c/38644] " davejmurphy at me dot com 2009-03-17 0:03 ` [Bug target/38644] " rearnsha at gcc dot gnu dot org 2009-11-23 16:42 ` pinskia at gcc dot gnu dot org 2009-12-21 21:47 ` pinskia at gcc dot gnu dot org 2009-12-22 11:16 ` rearnsha at gcc dot gnu dot org [this message] 2009-12-22 11:38 ` [Bug rtl-optimization/38644] " steven at gcc dot gnu dot org 2009-12-22 11:58 ` rearnsha at gcc dot gnu dot org 2009-12-22 12:07 ` jakub at gcc dot gnu dot org 2009-12-22 13:33 ` rearnsha at gcc dot gnu dot org 2009-12-22 14:08 ` steven at gcc dot gnu dot org 2009-12-22 14:35 ` cwang at rossvideo dot com 2009-12-22 14:58 ` pinskia at gcc dot gnu dot org 2010-05-13 14:22 ` pinskia at gcc dot gnu dot org 2010-05-17 9:05 ` sebastian dot huber at embedded-brains dot de 2010-05-26 12:44 ` mikpe at it dot uu dot se 2010-06-06 19:17 ` mikpe at it dot uu dot se 2010-06-10 7:14 ` sebastian dot huber at embedded-brains dot de 2010-08-12 8:19 ` sebastian dot huber at embedded-brains dot de 2010-08-12 10:00 ` [Bug rtl-optimization/38644] [4.3/4.4/4.5/4.6 Regression] " steven at gcc dot gnu dot org 2010-08-12 10:01 ` steven at gcc dot gnu dot org 2010-08-12 10:08 ` steven at gcc dot gnu dot org 2010-08-12 10:12 ` amonakov at gcc dot gnu dot org 2010-08-12 11:37 ` steven at gcc dot gnu dot org 2010-08-12 11:48 ` jakub at gcc dot gnu dot org 2010-08-12 12:00 ` amonakov at gcc dot gnu dot org 2010-08-12 12:04 ` rguenth at gcc dot gnu dot org 2010-08-12 12:13 ` rearnsha at gcc dot gnu dot org 2010-08-12 12:26 ` jakub at gcc dot gnu dot org 2010-08-12 12:31 ` rearnsha at gcc dot gnu dot org 2010-08-30 15:48 ` rguenth at gcc dot gnu dot org 2010-08-30 18:59 ` mikpe at it dot uu dot se
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=20091222111641.28673.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).