public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mircea.namolaru at inria dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/62630] [5 regression] gcc.dg/graphite/vect-pr43423.c FAILs
Date: Fri, 20 Feb 2015 00:45:00 -0000	[thread overview]
Message-ID: <bug-62630-4-EooM77UsVd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-62630-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62630

--- Comment #16 from Mircea Namolaru <mircea.namolaru at inria dot fr> ---
Yes, but it seems to me that the cast (not in the original code) should not
be generated at all if it could not be guaranteed that the casted-to type is
larger 
enough to accommodate it. Otherwise you introduce a cast from a longer signed
type
to a shorter signed one whose behaviour is undefined by the C standard and was
not
in the original code.

So the cast in the following code is problematic (when
graphite_IV, a signed long is not in the range of a signed int).

       _56 = (intD.6) graphite_IV.5_53;
       _55 = aD.1830[_56];

The solution to fix this is to made Graphite not to generate
casts like this. An alternative is to infer the range of
graphite_IV like you do and remove the cast (but this seems more complicated
and risky as the analysis may not succeed and the problematic cast is not
removed).


  parent reply	other threads:[~2015-02-20  0:45 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-01 13:21 [Bug tree-optimization/62630] New: " ro at gcc dot gnu.org
2014-09-01 13:24 ` [Bug tree-optimization/62630] " ro at gcc dot gnu.org
2014-09-01 13:26 ` ro at gcc dot gnu.org
2014-09-01 13:32 ` ktkachov at gcc dot gnu.org
2014-11-24 13:13 ` rguenth at gcc dot gnu.org
2015-01-19 13:10 ` rguenth at gcc dot gnu.org
2015-02-12 13:17 ` jakub at gcc dot gnu.org
2015-02-17 10:49 ` rguenth at gcc dot gnu.org
2015-02-17 20:12 ` mircea.namolaru at inria dot fr
2015-02-18 11:23 ` rguenth at gcc dot gnu.org
2015-02-18 11:34 ` rguenth at gcc dot gnu.org
2015-02-18 11:57 ` mircea.namolaru at inria dot fr
2015-02-18 13:03 ` rguenth at gcc dot gnu.org
2015-02-18 15:06 ` rguenth at gcc dot gnu.org
2015-02-18 15:25 ` rguenth at gcc dot gnu.org
2015-02-18 23:34 ` mircea.namolaru at inria dot fr
2015-02-19 10:19 ` rguenth at gcc dot gnu.org
2015-02-20  0:45 ` mircea.namolaru at inria dot fr [this message]
2015-02-20 16:46 ` joseph at codesourcery dot com
2015-02-23 18:21 ` mircea.namolaru at inria dot fr
2015-03-09 14:40 ` jakub at gcc dot gnu.org
2015-03-25 13:14 ` [Bug tree-optimization/62630] [5/6 Regression] gcc.dg/graphite/vect-pr43423.c XFAILed rguenth at gcc dot gnu.org
2015-03-25 13:20 ` rguenth at gcc dot gnu.org
2021-05-14  9:47 ` [Bug tree-optimization/62630] [9/10/11/12 " jakub at gcc dot gnu.org
2021-06-01  8:06 ` rguenth at gcc dot gnu.org
2021-09-14  6:24 ` pinskia at gcc dot gnu.org
2022-05-27  9:35 ` [Bug tree-optimization/62630] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:31 ` jakub at gcc dot gnu.org
2023-07-07 10:30 ` [Bug tree-optimization/62630] [11/12/13/14 " rguenth at gcc dot gnu.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=bug-62630-4-EooM77UsVd@http.gcc.gnu.org/bugzilla/ \
    --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).