public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/30364] [4.1 Regression] Wrong variable ranges due to constant folding Date: Fri, 24 Aug 2007 16:40:00 -0000 [thread overview] Message-ID: <20070824164040.26497.qmail@sourceware.org> (raw) In-Reply-To: <bug-30364-7904@http.gcc.gnu.org/bugzilla/> ------- Comment #18 from rguenth at gcc dot gnu dot org 2007-08-24 16:40 ------- Maybe - I was just conservative here to not possibly introduce new overflow with the re-association as elsewhere we may rely on the undefinedness of overflow. Another way to fix this particular regression is to disable the decomposing of &a->v[x - 2147483646] to pointer arithmetic in the C frontend here: /* For &x[y], return x+y */ if (TREE_CODE (arg) == ARRAY_REF) { tree op0 = TREE_OPERAND (arg, 0); if (!c_mark_addressable (op0)) return error_mark_node; return build_binary_op (PLUS_EXPR, (TREE_CODE (TREE_TYPE (op0)) == ARRAY_TYPE ? array_to_pointer_conversion (op0) : op0), TREE_OPERAND (arg, 1), 1); } like I tried a couple of times. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30364
prev parent reply other threads:[~2007-08-24 16:40 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-01-04 9:16 [Bug c/30364] New: " guillaume dot melquiond at ens-lyon dot fr 2007-01-04 9:30 ` [Bug middle-end/30364] [4.1/4.2/4.3 Regression] " pinskia at gcc dot gnu dot org 2007-01-04 10:15 ` guillaume dot melquiond at ens-lyon dot fr 2007-01-04 10:23 ` pinskia at gcc dot gnu dot org 2007-01-04 10:26 ` pinskia at gcc dot gnu dot org 2007-01-04 10:40 ` pinskia at gcc dot gnu dot org 2007-01-04 11:25 ` guillaume dot melquiond at ens-lyon dot fr 2007-01-05 19:06 ` jakub at gcc dot gnu dot org 2007-01-05 19:58 ` pinskia at gcc dot gnu dot org 2007-01-05 20:32 ` pinskia at gcc dot gnu dot org 2007-01-05 21:06 ` gdr at integrable-solutions dot net 2007-01-05 21:09 ` gdr at integrable-solutions dot net 2007-02-05 5:50 ` mmitchel at gcc dot gnu dot org 2007-02-14 9:03 ` mmitchel at gcc dot gnu dot org 2007-02-21 14:24 ` rguenth at gcc dot gnu dot org 2007-02-28 21:57 ` rguenth at gcc dot gnu dot org 2007-02-28 23:03 ` [Bug middle-end/30364] [4.1/4.2 " rguenth at gcc dot gnu dot org 2007-03-05 13:15 ` rguenth at gcc dot gnu dot org 2007-03-05 13:17 ` [Bug middle-end/30364] [4.1 " rguenth at gcc dot gnu dot org 2007-03-15 18:09 ` rguenth at gcc dot gnu dot org 2007-03-15 18:10 ` rguenth at gcc dot gnu dot org 2007-08-24 16:33 ` jakub at gcc dot gnu dot org 2007-08-24 16:40 ` rguenth at gcc dot gnu dot org [this message]
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=20070824164040.26497.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).