public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bonzini at gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/45472] [4.5/4.6 Regression] ICE: in move_op_ascend, at sel-sched.c:6124 with -fselective-scheduling2 Date: Mon, 18 Oct 2010 12:21:00 -0000 [thread overview] Message-ID: <20101018122100.XHxrzWApRNFbTECbVf6FMZVDN1-JCnNanUwOIuvVKH4@z> (raw) In-Reply-To: <bug-45472-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45472 --- Comment #8 from Paolo Bonzini <bonzini at gnu dot org> 2010-10-18 12:20:39 UTC --- Would it make sense to make the statement volatile even if only some subcomponents (or all subcomponents) are volatile? I like (2); if I understand it correctly, in this case vv1 and vv2 would not be volatile, but you'd still have vv1 ={v} vv2; in the GIMPLE source. It should be possible to use a bit on {ARRAY,RECORD,UNION,QUAL_UNION}_TYPE to cache this, e.g. #define TYPE_HAS_VOLATILE_PARTS(T) \ (AGGREGATE_TYPE_P (T) \ ? TYPE_UNSIGNED (T) \ : TYPE_VOLATILE (T)) #define AGGREGATE_TYPE_CHECK(T) \ TREE_CHECK4(T, ARRAY_TYPE, RECORD_TYPE, UNION_TYPE, QUAL_UNION_TYPE) #define SET_TYPE_HAS_VOLATILE_PARTS(T, V) \ (TYPE_UNSIGNED (AGGREGATE_TYPE_CHECK (T)) = (V)) Separately, expand would of course need to be taught about expanding accesses to volatile subcomponents as mem/v. If this approach was feasible, it would have the advantage of splitting the task in two parts, one for GIMPLE (including possibly the verifier) and one for expand.
next prev parent reply other threads:[~2010-10-18 12:21 UTC|newest] Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-45472-4@http.gcc.gnu.org/bugzilla/> 2010-10-18 10:57 ` abel at gcc dot gnu.org 2010-10-18 11:47 ` matz at gcc dot gnu.org 2010-10-18 12:21 ` bonzini at gnu dot org [this message] 2010-10-18 15:43 ` rguenth at gcc dot gnu.org 2010-10-18 15:58 ` matz at gcc dot gnu.org 2010-10-18 16:41 ` joseph at codesourcery dot com 2010-10-18 17:13 ` bonzini at gnu dot org 2010-12-16 13:09 ` rguenth at gcc dot gnu.org 2011-01-13 10:35 ` abel at gcc dot gnu.org 2011-04-08 6:42 ` [Bug middle-end/45472] [4.5/4.6/4.7 " abel at gcc dot gnu.org 2011-04-28 15:08 ` rguenth at gcc dot gnu.org 2011-12-10 5:52 ` pinskia at gcc dot gnu.org 2012-01-19 9:38 ` abel at gcc dot gnu.org 2012-02-16 19:52 ` [Bug middle-end/45472] [4.5/4.6/4.7 Regression] [Middle-end volatile semantics] " jason at gcc dot gnu.org 2012-02-16 20:59 ` zsojka at seznam dot cz 2012-02-20 11:55 ` rguenth at gcc dot gnu.org 2012-02-27 9:18 ` ebotcazou at gcc dot gnu.org 2012-07-02 11:20 ` [Bug middle-end/45472] [4.5/4.6/4.7/4.8 " rguenth at gcc dot gnu.org 2013-01-05 21:12 ` [Bug middle-end/45472] [4.6/4.7/4.8 " dje at gcc dot gnu.org 2013-01-05 21:44 ` zsojka at seznam dot cz 2013-02-26 9:22 ` abel at gcc dot gnu.org 2013-02-27 8:56 ` abel at gcc dot gnu.org 2013-02-27 9:04 ` [Bug middle-end/45472] [4.6/4.7 " abel at gcc dot gnu.org 2013-04-03 6:00 ` abel at gcc dot gnu.org 2013-04-12 15:16 ` [Bug middle-end/45472] [4.7 " jakub at gcc dot gnu.org 2014-06-12 12:58 ` rguenth at gcc dot gnu.org 2010-08-31 23:57 [Bug rtl-optimization/45472] New: [4.5/4.6 Regression] " zsojka at seznam dot cz 2010-08-31 23:58 ` [Bug rtl-optimization/45472] " zsojka at seznam dot cz 2010-09-01 3:03 ` hjl dot tools at gmail dot com 2010-09-01 9:46 ` rguenth at gcc dot gnu dot org 2010-09-02 11:28 ` rguenth at gcc dot gnu dot org 2010-09-20 13:05 ` abel at gcc dot gnu dot org 2010-09-20 14:50 ` amonakov at gcc dot gnu dot org 2010-09-20 16:02 ` bonzini at 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=20101018122100.XHxrzWApRNFbTECbVf6FMZVDN1-JCnNanUwOIuvVKH4@z \ --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).