public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/59649] [4.9 regression] conftest.c miscompiled
Date: Mon, 06 Jan 2014 09:59:00 -0000	[thread overview]
Message-ID: <bug-59649-4-RRZVHpwmNE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59649-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59649

--- Comment #4 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> So, IMHO either get_mode_bounds needs to special case BImode like
> trunc_int_for_mode does and make the bounds of BImode include values of 0
> and STORE_FLAG_VALUE, or the BImode hunk in trunc_int_for_mode needs to be
> dropped and everything analyzed for assumption that BImode true is CONST_INT
> equal to STORE_FLAG_VALUE, or ia64 needs to use STORE_FLAG_VALUE -1 (there
> is a comment about it in ia64.h that it should be investigated).

Given that ia64 is barely maintained these days, the 3rd approach doesn't look
very realistic and the 2nd one a little risky, so the 1st approach is very
likely the way to go I'd think (e.g. if_then_else_cond also special-cases
BImode).


  parent reply	other threads:[~2014-01-06  9:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-31 11:27 [Bug rtl-optimization/59649] New: " schwab@linux-m68k.org
2013-12-31 13:24 ` [Bug rtl-optimization/59649] " schwab@linux-m68k.org
2014-01-02 14:52 ` ebotcazou at gcc dot gnu.org
2014-01-06  9:39 ` jakub at gcc dot gnu.org
2014-01-06  9:59 ` ebotcazou at gcc dot gnu.org [this message]
2014-01-07 18:05 ` jakub at gcc dot gnu.org
2014-01-07 19:17 ` jakub at gcc dot gnu.org
2014-01-07 23:05 ` ebotcazou at gcc dot gnu.org
2014-01-08 10:01 ` [Bug rtl-optimization/59649] [4.9 regression] BImode miscompiled jakub at gcc dot gnu.org
2014-01-08 10:02 ` jakub 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-59649-4-RRZVHpwmNE@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).