public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "belagod at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/64032] [5 Regression] FAIL: gcc.dg/undefined-loop-2.c  (test for warnings, line 18)
Date: Thu, 11 Dec 2014 17:47:00 -0000	[thread overview]
Message-ID: <bug-64032-4-8o4WqD2Zwl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64032-4@http.gcc.gnu.org/bugzilla/>

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

Tejas Belagod <belagod at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |belagod at gcc dot gnu.org

--- Comment #4 from Tejas Belagod <belagod at gcc dot gnu.org> ---
Also fails on aarch64.

$ aarch64-none-elf-gcc -O2 -Waggressive-loop-optimizations -S
/work/dev/arm/src/gcc/gcc/testsuite/gcc.dg/undefined-loop-2.c
/work/dev/arm/src/gcc/gcc/testsuite/gcc.dg/undefined-loop-2.c: In function
'foo':
/work/dev/arm/src/gcc/gcc/testsuite/gcc.dg/undefined-loop-2.c:19:8: warning:
loop exit may only be reached after undefined behavior
[-Waggressive-loop-optimizations]
        && i < 100;   /* { dg-warning "loop exit may only be reached after
undefined behavior" } */
        ^
/work/dev/arm/src/gcc/gcc/testsuite/gcc.dg/undefined-loop-2.c:17:17: note:
possible undefined statement is here
         : array2[i]) /* { dg-message "note: possible undefined statement is
here" } */
                 ^
/work/dev/arm/src/gcc/gcc/testsuite/gcc.dg/undefined-loop-2.c:16:17: note:
possible undefined statement is here
         ? array1[i]  /* { dg-message "note: possible undefined statement is
here" } */


  parent reply	other threads:[~2014-12-11 17:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-23 15:30 [Bug c/64032] New: " danglin at gcc dot gnu.org
2014-11-24 11:15 ` [Bug middle-end/64032] [5 Regression] " rguenth at gcc dot gnu.org
2014-12-10 15:40 ` [Bug testsuite/64032] " rguenth at gcc dot gnu.org
2014-12-11 17:47 ` belagod at gcc dot gnu.org [this message]
2014-12-24 14:27 ` ams at gcc dot gnu.org
2014-12-24 14:29 ` ams 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-64032-4-8o4WqD2Zwl@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).